Event Mesh
Emitting and consuming business events across systems — brokered delivery, subscription management, and the mapping between CDS events and a broker topic. Which broker sits in between is the decision: SAP Cloud Application Event Hub between SAP cloud applications, an Integration Suite event broker in a heterogeneous landscape. The reliability questions — outbox, retries, ordering — belong to async processingAsync processingDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.SAP and community, narrow by design rather than here.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Connects CAP Java's messaging service to SAP Integration Suite, advanced event meshSAP Integration Suite, advanced event meshAn event streaming, event management and monitoring platform for event-driven architecture, offered within SAP Integration Suite.sap official, btp: setting a service's kind to aem routes events to the Solace-based broker, which can reach systems outside SAP as well as inside it.
Connects a CAP messaging service to SAP Event MeshEvent MeshManaged queues and topics over AMQP, MQTT and a REST gateway, and the bus SAP's own applications publish their business events to.sap official, btp, so the application can publish and subscribe to events through it once the service instance is bound.
Sets a CAP Java messaging service's kind to event-hub, so it sends and receives through SAP Cloud Application Event HubSAP Cloud Application Event HubDistributes the business events SAP cloud applications publish to the other SAP cloud applications in a landscape, with subscriptions managed in its own UI and no topics or queues to configure.sap official, btp instead of another broker, with no topics or queues for the application to declare.
Connects a CAP messaging service to Apache Kafka for intra-application messaging, using the Kafka client library directly rather than a managed SAP broker.
Connects a CAP messaging service to RedisRedisAn in-memory data store. For the things here it is the shared cache, the queue or the pub/sub channel that lets several application instances behave as one. Pub/Sub as a beta broker, where every subscribed application instance receives the same broadcast event and delivery is not guaranteed.
Ships publish-subscribe messaging built into the runtime's core, including a file-based message broker that mocks a broker on the local file system for local testing; a real broker needs a separate Maven dependency for that broker.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Artifacts
Tasks
Receive messages from an Apache Kafka topic
Records that another system writes to a topic on an Apache Kafka cluster reach a handler in the application, which processes each one as an event.
Covers the path from the Kafka topic to the handler. Sending to Kafka is a separate task, and so is what the handler does when processing fails, which belongs to async processing. Which SAP services a subaccount is entitled to, and whether the application's network can reach the cluster, are project questions and are not assessed here.
SAP Integration Suite, advanced event meshA Kafka Receiver configured on the event broker reads records from one or more Kafka topics, converts each to a broker message and publishes it to a broker topic, without Kafka Connect in between. A substitution expression builds the broker topic from the Kafka topic. The Kafka topic, partition and offset arrive as user properties, and every Kafka header becomes a user property too.
Remaining work: Configure the Kafka Receiver and its topic bindings on the broker. The application still needs a client for the broker, which for CAP is one of the two advanced event mesh plugins below.
com.sap.cds:cds-feature-advanced-event-meshConnects CAP Java's messaging service to SAP Integration Suite, advanced event mesh once a messaging service's kind is aem. The README does not mention Kafka: the plugin receives what the broker delivers.
Conditions: A Kafka Receiver on the advanced event mesh broker publishes the Kafka records to a broker topic the application subscribes to
Remaining work: Add the Maven dependency, bind the application to the broker's validation service instance, and subscribe to the broker topic the Kafka Receiver publishes to.
com.sap.cds:cds-feature-kafkaSAP's list of CAP Java modules gives this feature one line, intra-application messaging with Apache Kafka, and its POM depends on the Apache Kafka client library. capire's Java messaging page documents Maven dependencies and a kind for SAP Event Mesh, SAP Cloud Application Event Hub, advanced event mesh and Redis, and none for Kafka. Whether the feature subscribes to a topic that another system writes to, and how it is configured to do so, is not documented.
Remaining work: Not established. The configuration would have to be read out of the module itself.
Details
Coverage
Designs that place it
For your agent
- Ref
capability:event-mesh- JSON
- /capabilities/event-mesh.json
- MCP
- Connecting an agent