Introduction
Solace Event Portal helps integration teams and developers work together to design, govern, and grow event-driven integrations and applications. This guide walks you through the journey — from setup to reuse — with short videos that show how quick and simple it is to get started.
By following these steps, you’ll:
- Accelerate adoption of event-driven architecture across your teams.
- Empower developers with self-service access.
- Give integration teams confidence with governance, visibility, and accurate documentation.
- Maximize the value of your Solace investment.
Modules
Once you sign in to Solace Event Portal, you’ll see four modules:
- With Designer, you can design and visualize every aspect of your event-driven system: create events, define payload schemas, map out application publishers and subscribers, and build event APIs and event API products to share events across your ecosystem.
- Catalog is where you’ll find everything you need to manage your event-driven system: applications, events, schemas, enumerations, and event APIs.
- Runtime Event Manager lets you create detailed models of your event-driven system using objects designed in Designer and/or real-time data collected from your event brokers.
- KPI Dashboard gives you a clear view of key performance indicators so you can monitor your system’s performance and efficiency.
This video will help you better understand what each of these modules are, and what you’ll do with each of them.
Components
Solace Event Portal lets you work with a few kinds of event-driven objects: applications, application domains, events, and schemas. This section describes what each of those is, and how they interact with each other.
Application Domains
Application domains help you organize your event-driven system into manageable pieces — by team, business unit, microservices, or any logical grouping. They also give you control over access and object management within each domain. This video will help you learn all about them.
Applications, Schemas, and Events
- Applications are the systems or services that produce or consume events – they can be programs, microservices, processes, external systems, or IoT devices.
- Schemas define the structure and data types of the payloads being sent as part of events. They ensure consistency by outlining how the data should be organized and validated.
- Events are messages that convey information about a change of state or action, like an order being placed or a sensor reading.
Watch the video to see how these are presented within Solace Event Portal.
Environments, Event Brokers and Modeled Event Meshes
- Environments represent the operational environments you use for software development lifecycle processes, such as development, test, UAT, and production.
- Modeled event meshes are representations of your actual event mesh that live within Event Portal so you can define and visualize event flows.
- Event brokers ensure the efficient distribution of events between producers and consumers across your system. The event brokers in Event Portal map to the actual event brokers in your runtime.
Watch this video to learn all about these components.
Why This Journey Matters
With Event Portal, it’s not just easy to get started — it’s easy to design, govern and grow your event-driven system. Developers move faster with self-service tools, integration teams ensure governance without bottlenecks, and your organization gets maximum value from its Solace platform investment.
Get started today and see how simple it is to build your first event-driven application!