Event Mesh
SAP BTP Event Mesh is a managed publish-subscribe messaging service that enables asynchronous, event-driven communication between SAP and non-SAP applications across Cloud Foundry, Kyma, and hybrid landscapes. This topic covers its business purpose, queue and topic design, security configuration, runtime message flow, integration with Integration Suite and S/4HANA, and production troubleshooting.
Overview
SAP BTP Event Mesh is a managed publish-subscribe messaging service that enables asynchronous, event-driven communication between SAP and non-SAP applications across Cloud Foundry, Kyma, and hybrid landscapes. This topic covers its business purpose, queue and topic design, security configuration, runtime message flow, integration with Integration Suite and S/4HANA, and production troubleshooting.
Lessons in this topic
- BTP Event Mesh Part 1: Why Event-Driven IntegrationSAP Event Mesh lets applications publish and consume events asynchronously. Learn topics, queues and subscriptions, publish/subscribe vs point-to-point, CloudEvents format, protocols (AMQP, MQTT, REST), and how events replace polling — plus how Event Mesh relates to SAP Integration Suite, advanced event mesh.
- BTP Event Mesh Part 2: Queues, Subscriptions and SecurityConfigure Event Mesh: service instance with a service descriptor (namespace, options, topic and queue rules), queues and topic subscriptions, webhooks for push delivery, OAuth client credentials for clients, and least-privilege rules for publish/consume.
- BTP Event Mesh Part 3: Reliable Event ConsumptionConsume events without losing them: persistent queues, acknowledgements after successful processing, redelivery on failure, maximum redelivery and dead message queues, consumer scaling, and monitoring queue depth.
- BTP Event Mesh Part 4: Event-Driven Architecture Design on BTPDesign event-driven landscapes: topic hierarchy and naming, notification vs data-carrying events, one queue per consumer, fan-out and decoupling, event versioning, combining events with APIs (event + lookup), and when Advanced Event Mesh fits better.
- BTP Event Mesh Part 5: Delivery Guarantees, Ordering and Idempotent ConsumersHandle the realities of event delivery: at-least-once semantics, duplicate events, ordering limits, idempotent consumer design with event IDs and business keys, out-of-order handling with version/timestamps, and reconciliation jobs.
- BTP Event Mesh Part 6: S/4HANA Business Events to Event MeshConnect S/4HANA to Event Mesh: Enterprise Event Enablement, channel configuration to the Event Mesh instance, outbound bindings for standard business events (topics), event formats from SAP Business Accelerator Hub, consuming events in CAP or Integration Suite, and monitoring.
Interview questions covered
- What are the core concepts of Event Mesh, and how would you explain them clearly in an SAP interview?
- How would you apply Event Mesh in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in Event Mesh. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in Event Mesh?
- Suppose you inherit an existing Event Mesh solution. How would you review it before making a change?
- Connect S/4HANA business events to Event Mesh and consume them in a CAP app.
- A retailer polls S/4 for changes every few minutes. Explain Event Mesh and how events would help.
- Set up Event Mesh for an orders application with several consumers.
- Events are occasionally lost or block processing. How do you make consumption reliable?
- Design an event-driven architecture for sales order changes consumed by CRM, data warehouse and a mobile app.
- A consumer applied the same event twice and older events overwrote newer data. How do you design consumers?