Solace and the Event Mesh: Building real-time event distribution

The more connected an enterprise becomes, the harder it can be to keep its systems independent.

Connecting applications is an essential part of how enterprises operate, and at first it can feel like straightforward progress: information can move between systems, new consumers can be added and business events can become available beyond the applications where they originate. But there is a point where connecting more systems starts to create a problem of its own: the systems producing those events become increasingly responsible for knowing who needs them, where they are and how they should receive them.

A business event that starts with one consumer can eventually become relevant to applications, analytics, automation, partners and AI services across different environments and business domains. The more useful that event becomes, the more relationships can form around it, and an architecture intended to reduce coupling can gradually begin to accumulate it instead.

This is where the problem becomes architectural rather than simply operational. If every new consumer requires another relationship with the producer, the application that knows what happened also becomes increasingly concerned with everything that happens afterwards. As the enterprise evolves, that distribution responsibility can become embedded in applications that were never designed to carry it.

But why should the producer need to know?

What if an application could focus on communicating that something meaningful had happened, without having to understand every system, service or process that might eventually be interested in that information? What if the responsibility for deciding where an event should travel could sit elsewhere, allowing new consumers to appear without continually adding new dependencies to the producer?

That shift in responsibility sits at the heart of the Event Mesh.

Separating the producer from the distribution of its events may sound straightforward, but making that model work across a real enterprise is considerably harder when business events need to travel across on-premises systems, multiple clouds and external ecosystems without creating new dependencies between producers and consumers as the architecture evolves.

What is an Event Mesh?

An Event Mesh is an architectural layer that connects distributed event brokers, allowing business events to move dynamically between producers and consumers across different environments.

The distributed nature of the architecture is fundamental to understanding its role. A single event broker can provide effective publish-subscribe messaging within a particular environment, but enterprise technology rarely exists in one place. Applications may operate across multiple public clouds, private infrastructure, on-premises environments and regional platforms, while partners and external consumers may sit outside the organisation altogether.

An Event Mesh connects those distributed event environments into a wider network through which relevant events can travel.

Applications can remain connected to event infrastructure appropriate to their local environment, while the mesh provides the wider distribution required to make events available elsewhere. The producing application does not need to know which broker serves the consumer, which cloud it is running in or how many other subscribers are interested in the same event.

Instead, its responsibility is to produce an accurate representation of the business activity that occurred, while the Event Mesh takes responsibility for determining how that event needs to move through the wider enterprise.

Why do enterprises need an Event Mesh?

Enterprises rarely operate within a single technology environment.

Acquisitions introduce new platforms and environments, while cloud migration creates hybrid architectures in which modern workloads coexist with systems that remain on premises. Organisations may operate across multiple regions for performance, resilience or regulatory reasons, while partners increasingly require controlled access to operational information.

The result is an enterprise in which business activity happens across many different technical and organisational boundaries, while the events representing that activity may need to create value far beyond the environment in which they originated.

Without a distributed event layer, organisations can find themselves recreating dependencies between those environments. Applications may be forced to connect back to central infrastructure, or individual integrations may be introduced whenever information needs to move between separate event environments. As the landscape grows, those relationships become increasingly difficult to maintain.

An Event Mesh provides another model by allowing distributed event brokers to form part of a connected event layer. Applications can remain close to the infrastructure serving their environment, while business events travel through the wider mesh towards authorised consumers elsewhere.

This means organisations can extend event-driven architecture across their technology landscape without having to centralise the environments in which those events originate.

Local connectivity with enterprise-wide reach

This model becomes particularly valuable as the location and composition of enterprise applications change over time.

A consumer may initially operate in the same environment as the producer and later move to another cloud. A new regional application may begin using an event that previously had only local consumers, while a partner or newly acquired business may introduce another legitimate destination for the same business information.

If the producer is directly responsible for those relationships, each change can create another dependency on the source application. Within an Event Mesh, however, the producer can continue publishing the same business event while the event infrastructure handles the changing distribution requirements.

The result is an architecture in which applications can remain locally connected while business events gain enterprise-wide reach, allowing the underlying technology landscape to evolve without forcing producers and consumers to change in lockstep.

Intelligent routing rather than intelligent producers

One of the defining characteristics of an Event Mesh is the separation between producing business events and understanding the topology through which those events need to travel.

A business application should not need to understand which environments contain interested consumers, which broker should receive an event next, whether another application has started subscribing or whether a new partner or AI service has become an authorised consumer. Those concerns belong to the event distribution architecture, not the producing application.

If an application publishes an OrderConfirmed event, its responsibilities should not multiply simply because additional consumers become interested in that event six months later. The Event Mesh allows those new consumers to participate without turning each new use case into another integration project for the originating system.

This separation has an important effect on architectural adaptability. When applications, partners or services can begin consuming existing events without modifications to the originating systems, the source application no longer needs to become the integration bottleneck whenever a new use case appears.

Events follow subscriber demand

The difference becomes more significant when the number and location of consumers begin to change.

Traditional integrations frequently begin with a predetermined relationship between a source and a destination. The architecture knows that information must travel from one particular system to another and the integration is designed accordingly.

Within an Event Mesh, distribution can instead respond to subscriber demand. Consumers express interest in relevant event topics, while the event infrastructure determines how matching events need to travel through the mesh to reach those consumers.

This changes how event flows can evolve across the enterprise. Consumers can appear, disappear or move between environments without requiring the distribution model to be redesigned around each change. Routing becomes a responsibility of the event infrastructure, allowing event flows to adapt as subscriber demand changes.

From fixed connections to dynamic event distribution

The difference becomes clearer when the two models are placed side by side.

In a traditional point-to-point model, the producer participates directly in multiple integration relationships. As consumers multiply, those relationships can multiply with them, making changes elsewhere in the enterprise increasingly relevant to the producing system.

With an Event Mesh, the producer publishes the business event into the event infrastructure while consumers independently express their interest. The distribution layer assumes responsibility for connecting the two.

Point-to-Point Integration vs Event Mesh: A comparison of traditional point-to-point integration and an Event Mesh, showing how event-driven architecture decouples producers from consumers and enables dynamic event distribution across the enterprise.

The difference represents a change in architectural responsibility: the producer understands the business event, while the Event Mesh understands how that event needs to move across the enterprise.

How does Solace Event Mesh work?

Within the Digital Event Backbone described in Beyond Batch, Solace provides the distributed event movement required to connect producers and consumers across complex enterprise environments. Rather than forcing applications to understand how information should travel between locations, the Event Mesh creates a communication layer through which business events can move according to subscriber demand.

This becomes particularly valuable in an enterprise landscape that rarely exists in one place. Business activity may originate in on-premises data centres, private clouds, AWS, Azure, Google Cloud or SaaS platforms, while the consumers of those events may include enterprise applications, analytics platforms, AI assistants, automation services, mobile applications, partners, data platforms and digital twins.

The Event Mesh connects these environments without requiring every producer to establish and maintain individual relationships with every consumer. Applications publish business events into the event infrastructure, while the mesh determines how those events should travel across the distributed landscape to reach interested and authorised subscribers.

This is what allows the Event Mesh to operate as more than a collection of individual event brokers. A distributed mesh allows event routing to span environments while capabilities such as policy and access enforcement, observability, replay and resilience operate across the event distribution layer.

An Event Mesh creates a distributed communication layer across on premises, cloud and SaaS environments, allowing business events to reach multiple consumers without requiring producers to understand where those consumers operate.

The architecture shown above illustrates an important shift: the complexity of event distribution moves away from individual business applications and into the event infrastructure itself. As environments and consumers change, producers can continue publishing the same business events while the mesh manages how those events are distributed across the enterprise.

Distributed event routing

Distributed event routing allows business events to move across the mesh according to where authorised subscriber demand exists.

A producer can publish into its local event environment while the mesh determines how matching events should travel through the connected infrastructure to reach interested consumers. Moving a consumer, introducing another region or adding an authorised subscriber can therefore happen without necessarily changing the application that produced the event.

Topic-based subscriptions

Topic-based subscriptions provide a flexible mechanism through which consumers express which business events are relevant to them.

Events can be organised through meaningful topic structures that allow consumers to subscribe according to their own requirements. The same business event can therefore support multiple consumers and use cases without requiring separate delivery logic for each destination.

This is what makes publish once, subscribe many practical at enterprise scale: the producer publishes the business event, while consumers independently determine which events are relevant to them.

Resilience, replay and observability

Once business events begin supporting operational processes across multiple environments, distribution also needs to be reliable and observable.

High availability and resilience help event infrastructure continue operating when individual components or environments experience disruption, while replay provides the ability to make historical events available again when consumers need to recover or reprocess them.

Observability provides insight into how events move across the distributed landscape, helping teams understand event flows and operational behaviour across an architecture that may span multiple clouds, data centres and other environments.

Together, these capabilities allow the Event Mesh to support scenarios in which real-time event movement becomes an operational dependency rather than simply another data feed.

Policy and access across the mesh

Distribution also requires control. The fact that an event can travel across clouds, regions and organisational boundaries does not mean that every consumer should be able to receive it.

Policy and access controls allow organisations to manage how events are distributed and which consumers can participate, while the wider architecture can apply security, identity, governance and compliance requirements across the event landscape.

This becomes particularly important as event distribution extends beyond internal applications towards partners, external services and AI consumers.

Events without borders

One of the most useful ways to understand the significance of an Event Mesh is to consider what happens when a business event needs to move beyond the boundaries of the environment where it originated.

Modern enterprises rarely operate within a single technology estate. Acquisitions introduce additional platforms, cloud migration creates hybrid architectures, partners require controlled information sharing and regulatory requirements can influence where applications and data operate. The business event itself, however, may remain relevant across all of those boundaries.

An event produced in one environment may be required by an operational application in another, by analytics running elsewhere or by an authorised partner outside the immediate enterprise boundary. An Event Mesh allows that distribution to extend across technical and organisational boundaries without making the producer responsible for each new destination.

This allows business events to become enterprise assets rather than application-specific messages, remaining useful as the landscape around the systems producing them changes.

Hybrid and multi-cloud without centralising everything

A distributed enterprise does not necessarily benefit from forcing every event-driven workload into a single central location.

Applications can participate through event infrastructure appropriate to their own environment while the mesh provides connectivity across the wider estate. This allows organisations to preserve the characteristics of individual environments while giving business events a consistent route across them.

This creates greater independence between the business contract represented by an event and the infrastructure through which that event happens to travel.

Extending events to partners and ecosystems

The same principle applies when events need to move beyond internal enterprise systems.

Partners, suppliers and external services may require controlled access to selected business activity, but those relationships need to be governed independently from the applications that produce the underlying events.

An Event Mesh allows event distribution to extend towards those environments while subscriptions, policies and governance determine which events should be available to which consumers. The producer can therefore remain focused on the business event itself rather than the growing number of organisations or systems that may eventually find it valuable.

Supporting new applications, partners and AI consumers

The value of this separation becomes even clearer when entirely new categories of consumers emerge.

New applications can subscribe without changing existing producers, partners can participate without redesigning operational systems and AI services can consume relevant events without requiring source applications to be rebuilt around them.

For AI consumers, the significance is primarily architectural. Once an AI service becomes an authorised consumer of a business event, the Event Mesh can make that event available without the producing application needing to know where the service operates or how it connects to the wider enterprise.

This becomes increasingly important as organisations move towards the Agentic Enterprise, where AI agents need not only access to enterprise capabilities but timely awareness of what is changing across the business. The Agentic Enterprise is useless without integration. Here's why explores the wider architectural requirements behind that model.

The result is an architecture in which new consumers can emerge around existing business events while the lifecycle of the originating application remains largely independent from the lifecycle of the services consuming its information.

How does an Event Mesh fit into a Digital Event Backbone?

An Event Mesh addresses an important architectural problem, but event distribution is not the same as a complete enterprise event strategy.

The Event Mesh addresses a specific question:

A Digital Event Backbone addresses the broader architecture around those events, including how meaningful business activity becomes governed, discoverable and reusable information that can be trusted across the enterprise.

The Event Mesh provides the operational distribution required to move events between environments, while the wider backbone addresses questions around meaning, governance, ownership and how events can remain useful beyond the systems in which they originated.

The Event Mesh provides the distributed movement layer within a Digital Event Backbone, allowing business events to travel across on premises, cloud and SaaS environments, while governance, security and integration capabilities ensure those events remain controlled, understandable and reusable across the enterprise.

The distinction matters because an organisation can become extremely effective at distributing events while still struggling with inconsistent definitions, unclear ownership, poor discoverability or incompatible representations of the same business activity. The movement layer is necessary, but it does not define what an event means.

Distribution is only one capability

Moving an event successfully does not guarantee that the information will be understood in the same way wherever it arrives.

Business events need to be discovered, interpreted, governed, secured and managed throughout their lifecycle if they are going to operate as trusted enterprise assets. An Event Mesh can ensure that an event reaches the appropriate consumer with the required operational characteristics, but it does not inherently determine whether every consumer interprets that event consistently.

If different applications describe the same business concept in different ways, distributing those representations more efficiently does not resolve the semantic inconsistency. If ownership is unclear, routing does not establish accountability, while changes to event contracts still need to be managed without undermining the consumers that depend on them.

Real-time distribution therefore solves the problem of movement, while the enterprise still needs to solve the problems of meaning, governance and control.

This distinction is fundamental to understanding where an Event Mesh fits within a wider real-time architecture: the Event Mesh enables communication, while the broader architecture must ensure that what is being communicated remains understandable and trustworthy.

From event distribution to enterprise understanding

Once business events can move efficiently across the enterprise, the next architectural challenge is ensuring that those events retain consistent meaning wherever they travel.

Governance needs to establish ownership and accountability, while security and policy determine how events can be used. Mediation and transformation may be required to reconcile different operational representations, and lifecycle management must allow event contracts to evolve without undermining the consumers that depend on them.

This is where integration and governance platforms such as WSO2 enter the picture, complementing the distributed event movement provided by Solace with capabilities around API management, enterprise integration, mediation, transformation, identity, policy enforcement, orchestration, observability and lifecycle management.

The architectural progression is important because moving information is one challenge; ensuring that the enterprise shares a consistent understanding of what that information means is another.

Together, these capabilities turn event distribution into a broader enterprise capability: one that can move business events wherever they are needed while preserving the governance and context required for those events to remain useful when they arrive.

Could your business events travel further without adding more dependencies?

As event-driven architecture expands, the opportunity is no longer simply to connect more systems, but to create an architecture in which new consumers can emerge without continually adding dependencies to the applications that produce business events.

Claria helps organisations design real-time technology landscapes that bring together event-driven architecture, integration, APIs, automation and AI, using Solace to make business events available across increasingly distributed enterprise environments.

Ready to explore how Solace Event Mesh could support your real-time architecture? Get in touch!

Jamie Carter

Share