Hope everyone is having a great week. I wanted to share my newest blog and video where I show how simple it can be to get started with Spring Cloud Stream using start.spring.io & of course a Solace PubSub+ Event broker.
If you've never done it, you should give it a shot! It only takes 5 minutes
Blog is here.
And Video on YouTube (Contains proof it only takes 5 minutes!):
Do you use REST-over-HTTP (GET, POST, etc.) for application communication? Would you like to know how to integrate traditional RESTful apps and microservices with event-driven asynchronous ones?
In this hands-on developer workshop attendees will learn how to configure a Solace PubSub+ broker to accept incoming REST requests, configure the Solace broker to pass incoming REST requests straight through, and build a Solace messaging application to consume and respond to incoming REST requests.
When - Two sessions
Microsoft Teams online session (link provided on registration)
Solace's PubSub+ Event Portal
Event Portal is our event management tool that lets developers create, design, share, and manage events within an event-driven architecture. Now before you say "Why should I care?" I want to take you through a little memory exercise.
I want you to sit back and think of the last time you were about to make a change to an existing application that interacted with your event broker. Maybe this was just a small change, just a quick fix. Or maybe it was something that was a big part of an even larger overhaul. Regardless of the size of the task, before you jumped in to make the change you probably spent a bit of time thinking about how that change would have downstream effects. We all want to mitigate risk and avoid bugs. Maybe you needed to see all the events that your application produces or consumes. Or perhaps you thought about all the different applications that end up consuming a particular event. Ok, now that you've got the memory fixed in your mind, I want to ask you a few questions about how you went about discovering and viewing the events, the schemas, and the downstream applications. Ready?
Were they easy to find?
Were they all in one place?
Were they easy to read and understand?
Was it easy to identify topic hierarchy, or where you want to publish/subscribe to events?
and probably most important...
Were they up to date?
If you answered "No" to any of these questions then you're going to want to keep reading.
What if I told you Event Portal takes away all that pain and more, and it does it for your favorite broker? Not just Solace PubSub+, but Kafka, and RabbitMQ, and ActiveMQ, and, and, and. You name it, event portal can help. Whether you have one broker type or many you're going to want to keep reading.
Alright here we go!
First you need an account. If you haven't signed up for PubSub+ Cloud yet, this is where you're going to find Event Portal and get started. You can sign up here for a free 60 day trial, or if your organization is already using Event Portal ask your team to be added as a user.
Once you're logged into PubSub+ Cloud you're going to see three main tools in the Event Portal section:
Use the designer to create new application domains, applications, events, and schemas and, most importantly, visualize the topology of your event driven architecture. Get a visual understanding of how everything works together (or doesn't!) and make educated decisions about how to effectively change your code.
Use the Catalog when you just need to find something. You'll see the list of all applications, events, and schemas that have been created and can quickly search through them to find what you need. If you're just getting started and doing a proof of concept you might start small. But even in a proof of concept you can quickly get to the point where the list of applications, events, and schemas starts to grow long. Now you can use the Event Catalog to quickly browse and search all existing objects.
Use the Catalog to browse and Search
View the revision history for any object
Use Discovery to automatically bring all of your existing events, applications, and schemas into the Designer so you don't have to manually add them one by one. This tool allows you to run a discovery agent on your broker that will capture a runtime
As of posting time Discovery is currently in Closed Beta. If you would like access to Discovery for your Event Portal, please email [email protected] and request access.
That's a wrap! Have you tried Event Portal? Let us know about your experience in the comments below.
Got a cool EDA or real-time project you've been working on? Want to talk about a cool tech or framework you used in your application that enhanced your development process for your event-driven application? What about Johny-Five for you IoT project or X-State for state management solutions? Cool tips & tricks for using Spring Cloud Streams? Want to share a story on a Solace use-case?
This is your moment to shine, share, learn and teach! We are launching our first ever Solace Community Lightning Talks on Wednesday, September 30th at Noon EST for 1.5 hours where we invite developers and thought leaders from the community and internally at Solace to share their experiences and cool project they worked on 🌟
The Solace Community Lightning Talks will be live streamed on our ever growing developer virtual events collection and will have the following format
1. Presentations/Demo will be a 10 minute long pre-recorded video OR live - we're easy going and want you to choose your comfortable approach.
2. 5 minutes Live Q&A with the audience and panel
3. Up to 5 lightning talks ⚡️
We would love to hear from you! Show us your interest by sending us an email to [email protected] with the subject line "Solace Community Lightning Talks" and mention what you would like to talk about with a small short simple and quick abstract. We will contact you shortly after to setup the logistics and rehearsals 😎
Ever wonder what all the various objects you see configured in the Solace broker that start with a # symbol?? E.g.:
You may have stumbled onto some of these while poking around in the PubSub+ Manager GUI or in CLI. In short: any object you find that starts with a # is a system-created object for internal use, and you don't need to worry about it, and you shouldn't try to delete or modify it.
Most of the objects mentioned above are automatically created when you a) create a new Message VPN; b) enable a particular feature (e.g. Replay, or DMR); or c) connect a client or bridge. As some examples.
Hope that helps anyone who is wondering what these are! Let me know if you want more details.