SAP Integration Suite, advanced event mesh, (sometimes abbreviated as AEM), is an enterprise-grade event-driven architecture platform provided within the SAP Business AI Platform portfolio. It enables real-time event streaming, decoupling, and messaging across hybrid and multi-cloud environments. The technical foundation of AEM is built around several core architectural components, protocols, and management features.
Architecture: Control Plane and Event Plane
The architecture of SAP Integration Suite, advanced event mesh is divided into two distinct operational layers:
- Control Plane: The management layer hosted by the service provider. It provides a centralized web interface and APIs for lifecycle management, broker provisioning, service monitoring, and security management. Administrators use the control plane to create, scale, and manage event broker services.
- Event Plane: The data plane where messaging traffic actually flows. Event brokers reside in the event plane and handle event routing, queuing, and protocol translation. The event plane offers flexible deployment options across public cloud providers, including Amazon Web Services, Microsoft Azure, and Google Cloud Platform, in both SAP-managed and customer-managed environments.
Core Event Broker Technology
The runtime foundation of SAP Integration Suite, advanced event mesh relies on enterprise-grade Solace event broker technology. Individual event brokers can be interconnected to form a dynamic event mesh. This event mesh acts as a configurable network of brokers that transparently routes events across public clouds, private clouds, and on-premises data centers. Event routing occurs dynamically based on active subscriptions, ensuring efficient network usage by transmitting messages only to destinations that require them.
To understand this concept more simply, an event broker functions as an intelligent distributor for application messages. Instead of systems connecting directly to one another, which creates complex dependencies, applications simply send their messages to the broker. When brokers connect across different locations, they form the event mesh, which automatically routes data only to the systems that need it.
A helpful way to visualize this architecture is through the analogy of a global postal system with offices in different cities:
- Event Brokers as Local Post Offices: Each data center or cloud region has its own broker, acting like a local post office. Together, these post offices form a single interconnected delivery network.
- Publishers as Senders: An application in New York generates an event, such as a new European order. It drops the message off at its local New York broker without needing to know the exact server address or location of the processing system in Europe.
- Subscribers as Receivers: A processing system in Frankfurt registers a subscription with its local Frankfurt broker for European order updates.
- Dynamic Routing: The mesh automatically routes the order message from New York to Frankfurt. Because an office in Tokyo did not request European order updates, no data is sent there, keeping global network traffic minimal and efficient.

Protocol Support and Native Translation
A key technical strength of SAP Integration Suite, advanced event mesh is its protocol-neutral architecture. The event brokers perform native, inline translation between different messaging standards without requiring external gateways or translation adapters. Supported protocols and standards include:
- AMQP (Advanced Message Queuing Protocol 1.0)
- MQTT (MQ Telemetry Transport 3.1.1 and 5.0)
- REST over HTTP and HTTPS
- JMS (Java Message Service 1.1)
- WebSockets
- SMF (Solace Message Format)
The ability of the event brokers to translate protocols natively in real time without external gateways relies on an internal unified data representation.
When a message enters an SAP Integration Suite, advanced event mesh broker via any supported protocol, such as MQTT from an IoT device or REST over HTTP from a web app, the broker's engine immediately parses the packet and converts it into a standardized internal message format.
This internal conversion separates the message into three fundamental layers:
- Payload Abstraction
- The actual business data (payload) is preserved in a protocol-agnostic byte array, preventing data alteration or payload corruption during transit.
- Header and Property Mapping
- Protocol-specific headers (such as MQTT topics, JMS properties, or HTTP headers) are automatically mapped to equivalent internal metadata fields.
- Quality of Service (QoS) Alignment
- The broker translates the delivery guarantees of the source protocol (e.g., MQTT QoS 1) to match the corresponding delivery semantics of the target protocol (e.g., JMS Guaranteed Delivery).
When a subscriber requests the message using a different protocol, such as AMQP or JMS, the broker reads the standardized internal message and instantly encodes it into the destination protocol's syntax right before transmitting it. Because this process happens entirely in-memory at the core broker layer, it delivers ultra-low latency native translation without the performance overhead or single-point-of-failure risks associated with external translation bridges.
High Availability and Fault Tolerance
To support mission-critical enterprise integration scenarios, SAP Integration Suite, advanced event mesh services use high-availability architecture patterns based on redundant broker triplets. A high-availability broker cluster consists of:
- Primary Active Node
- Handles active client traffic and message processing.
- Secondary Standby Node
- Synchronously mirrors state and message stores from the active node.
- Monitoring Node
- Serves as a tie-breaker to assist in quorum detection and automated failover decisions.
In the event of an infrastructure or hardware failure on the primary node, the standby node automatically takes over operations without loss of guaranteed messages.
Topic Hierarchy and Dynamic Routing
Messaging within SAP Integration Suite, advanced event mesh utilizes hierarchical topic structures, which allow precise categorization of events using dynamic slash-separated strings. Producers publish messages to specific topics, while consumers use exact matches or multi-level wildcards to subscribe to event streams. The event mesh continuously synchronizes topic subscriptions across all connected brokers, enabling dynamic publish-subscribe and queue-based routing.

