Today is an exciting day for Solace because we are making available the beta version of our second generation PubSub+ Event Portal. One of the best advantages of being first to market with an event management tool for event driven architecture is that we get to collaborate with our users on what can be improved and what they need to make this product more powerful.
It was always Solace’s vision to add lifecycle management capabilities to PubSub+ Event Portal, and now we have that, plus much more. Organizations can now manage, govern, and integrate event flows across the enterprise. To say we’re excited about how much easier it is for companies to adopt and optimize their event-driven architecture with this second generation of our event portal is an understatement. But, in the end we want to hear from you as to whether it is indeed more valuable.
You can watch this short video from our Principal Product Manager, Darryl MacRae that takes you through a short introduction of the rich capabilities included in this beta release OR you can keep reading.
To get access to the second-generation beta version, use the toggle to select New Event Portal 2.0” to “On”. You can easily toggle back and forth between the two PubSub+ Event Portal versions.
The new key capabilities available to you are:
Multiple versions of applications produce and consume different events as they evolve. As new versions are created and promoted along the software delivery path from development to quality assurance to pre-production to production, enterprises need a mechanism to keep the production environment stable. The same type of promotion occurs with the underlying event and schema versions. This also requires that you be able to version these artifacts so you can have different versions of the same event or schema in dev, QA, pre-prod, and prod as you evolve them or deprecate them. Without this type of lifecycle management, if you have a few 100 or 1000s of events across 3-4 environments, how can you possibly manage the interdependencies of shared schemas, events or applications without negative impacts?
In this video below, Darryl MacRae demonstrates the power of managing the lifecycle of events in a retail scenario. Using an example, he shows how to determine why an order management system was publishing order status events without the customer ID and then adds the new version of the application to the dev environment for testing before promoting it to production.
For more information about these new features, please view the beta documentation at Event Portal 2.0 Overview
If you have a learning subscription at Solace Academy you can take the PubSub+ Cloud Event Portal Fundamentals Course to learn more as well.
Sandra Thomson is the Director of Product Marketing at Solace.[position] => [url] => https://solace.com/blog/author/sandra-thomson/ ) )
Sign-up to get access to:
Messaging Services – One Enterprise Developer Service with up to 100 connections/queues, 8 Gbps of throughput and 2 GB of storage
Event Portal – 150 Editor Users and 15,000 objects (an object is defined as an event, schema, or app)