SAP Integration Suite, advanced event mesh provides a cloud-native, enterprise-grade event-driven architecture (EDA) layer designed to connect disparate applications across hybrid, multi-cloud, and on-premises environments. Unlike traditional request-driven architectures (such as synchronous REST or SOAP calls), an event-driven architecture relies on asynchronous state changes (events) to trigger actions across distributed systems.
Key Architecture Principles
- Asynchronous Decoupling
Event producers publish events without needing to know which downstream applications will consume them or whether those consumers are currently online.
- Real-Time Data Flow
Information about business state changes (such as order creation, inventory updates, or master data changes) is distributed immediately as events occur.
- Protocol Translation & Multiprotocol Support
The architecture enables communication across diverse protocols (AMQP, MQTT, REST, JMS, and SMF/Solace Web Messagin) allowing legacy systems, modern cloud microservices, and IoT devices to interact seamlessly without converter middleware.
Core Operational Components
The Event Broker Service serves as the central runtime unit of SAP Integration Suite, advanced event mesh, operating as a fully managed messaging engine hosted on dedicated cloud infrastructure. Within this broker service, message queues store messages persistently until they are consumed and acknowledged by subscriber applications, guaranteeing reliable point-to-point and publish/subscribe delivery even during downstream system outages. Events are published using hierarchical topic strings, such as sap/s4/order/created/v1, which allows subscribers to use wildcard matching, like sap/s4/*/created/>, to dynamically receive targeted subsets of event streams. Overall security and isolation within the broker service are maintained through client profiles, access control lists, and client usernames, regulating precisely which applications are authorized to publish or subscribe to specific topics and queues.

Event Mesh Topologies & Hybrid Network Mesh
An Event Mesh is created by interconnecting multiple individual Event Broker Services across different cloud hyperscalers, such as AWS, Azure, and GCP, as well as Dedicated Regions like on-premises data centers or private clouds. To establish this mesh topology, inter-broker links known as Mesh Links create secure, high-throughput communication bridges between nodes operating in different regions. Through Dynamic Message Routing, the event mesh dynamically tracks active subscriptions across all connected brokers. When an event is published on Broker A, the mesh forwards the message over the mesh link to Broker B only if an application connected to Broker B has a matching active subscription. This selective dynamic routing prevents unwanted event traffic from traversing regional network boundaries, effectively reducing data transfer costs and minimizing latency.
Operational Paradigms: Event Streaming vs. Message Queuing
SAP Integration Suite, advanced event mesh supports both fundamental messaging paradigms within the same unified architecture:
| Feature | Message Queueing (Point-to-Point) | Event Streaming (Pub/Sub) |
|---|---|---|
| Delivery Model: | One-to-one delivery via named queues. | One-to-many distribution via hierarchical topics. |
| Persistence: | Messages are retained in queues until consumed and acknowledged. | Events are broadcast to matching subscribers in real time. |
| Primary Use Case: | Workload distribution, order processing, transactional task execution. | Business event broadcasting, real-time telemetry, master data updates. |