Lesson 2 of 6
Event Mesh vs Advanced Event Mesh
10 min
Listen to this lesson
Both of SAP's brokers publish and deliver events with topics and queues. The differences are in scale, deployment, features and pricing model, and they matter for Contoso's Wave 2 review. This lesson compares the two on the points SAP documents, then walks through Theo's decision.
Side by side
| Aspect | Event Mesh capability / SAP Event Mesh | SAP Integration Suite, advanced event mesh |
|---|---|---|
| Deployment | SAP BTP only | Dedicated event broker services on public clouds; also private cloud, on-premise and edge |
| Message size | 1 MB maximum per message (SAP Event Mesh documentation) | Much larger; SAP's comparison cites up to 30 MB on newer broker services |
| Protocols | AMQP 1.0 and MQTT 3.1.1 over WebSocket, plus REST/HTTP | SMF, AMQP, MQTT, REST, JMS, WebSockets |
| Multi-broker mesh | Single service per instance | Event mesh of brokers across regions and data centers with dynamic message routing |
| Replay | Not offered | Message replay from a replay log (check availability status for your tenant) |
| Partitioned queues | Not documented | Supported, for ordered processing per key with scaled consumers |
| Design and governance | Basic | Event Portal for cataloging events, schemas and applications |
| Monitoring | Basic queue and message views | Insights dashboards for broker health and message flow |
| Pricing model | Message-based | Broker-based (sized broker services) |
The two brokers compared, based on SAP's published comparisons and documentation. Limits change: verify on SAP Help for your plan and release.
What the differences mean
Size. Most S/4HANA business events are notifications that carry a key, far below 1 MB. Size matters for data events, documents or telemetry batches. Deployment. Advanced event mesh brokers can run close to producers, for example in a region near Monterrey or at the plant edge, and a mesh of brokers routes events between them, so a consumer in Detroit can subscribe to Monterrey events without a point-to-point link. Replay. A consumer can ask the broker to resend events from its replay log, from the beginning, from a time or after a message ID, which is how Elena's analytics consumer could reprocess a week. Partitioned queues let several consumer instances share a queue while events with the same key stay in order on one instance.
Theo's decision
- Is the consumer on SAP BTP and the event an SAP business event under 1 MB?Yes → Event Mesh capability is enough · No → next question
- Does the use case need replay, partitioned ordering or more than one region?Yes → advanced event mesh · No → next question
- Are producers or consumers on premise or at the plant edge?Yes → advanced event mesh broker near them · No → next question
- Will the volume or message size grow beyond the basic broker's limits?Yes → plan advanced event mesh now · No → stay on the Event Mesh capability
| Use case | Needs | Broker |
|---|---|---|
| Fleet order notifier | SAP events, BTP consumer, small payloads | Event Mesh capability (as today) |
| BPA fleet customer onboarding | SAP events, BTP consumer | Event Mesh capability (as today) |
| Warranty analytics | Replay of a week after a fix | Advanced event mesh (evaluation) |
| Monterrey plant events | Edge broker, regional routing, WAN tolerance | Advanced event mesh (evaluation) |
Theo's first mapping of Contoso's use cases (an evaluation, not a decided architecture).
If Contoso moves some flows to advanced event mesh, it will run two brokers for a while. Theo's rule: one broker per use case, never the same event consumed from both by one consumer, and SAP's migration guidance followed for anything that moves. Running both is a transition state with an end date, not a target architecture.
Questions to settle before a proof of concept
- Who operates the brokers? Advanced event mesh broker services are sized, upgraded and monitored; somebody on Theo's team needs that skill.
- Where do brokers run? A cloud region close to Monterrey, an edge broker in the plant, or both; each choice affects latency, cost and support.
- How do S/4HANA events reach the new broker? Check which channel types enterprise event enablement offers on Contoso's release, or whether events are bridged from the existing broker during transition.
- What does the contract allow? Broker sizes, regions and features depend on the subscription; Grace's procurement team checks before design starts.
What goes wrong
- Choosing by feature list. A broker with replay helps only if consumers are idempotent and topics are designed for replay.
- Two brokers forever. Without a migration plan, events are bridged in both directions and nobody knows which path delivered what.
- Assuming limits. Limits and availability (for example replay) differ by plan, broker version and tenant; test them.
What would you do?
Elena wants replay so the warranty analytics consumer can reprocess the last seven days after a bug fix. Theo proposes moving that use case to advanced event mesh. What should Priya insist the proof of concept shows?
- The Event Mesh capability fits SAP-centric events on BTP with small messages.
- Advanced event mesh adds deployment anywhere, a mesh across regions, larger messages, replay, partitioned queues, Event Portal and Insights.
- Choose per use case, prove features in the test stage, and keep coexistence temporary.
- Verify limits and feature availability for your plan; they change.
Check your understanding · not graded
Lesson check
1. What is the documented maximum message size for SAP Event Mesh?
2. Which feature lets a consumer get earlier events sent again?
3. What joins advanced event mesh brokers across regions?
4. How is advanced event mesh priced, per SAP's comparison?
5. Which Contoso use case most needs an edge broker?