topic Re: Event‑driven architecture in Artificial Intelligence Forum

Event‑driven architecture

Atul_Joshi85 — Mon, 06 Jul 2026 20:33:36 GMT

What are best practices for using SAP Event Mesh with AI services to handle real‑time utility events (like grid imbalance or meter exceptions)? For instance, a utility might route millions of smart meter events per day into Event Mesh. Joule or SAP AI Core could subscribe to those events, classify them (normal vs. exception), and trigger automated responses — such as opening a service ticket in S/4HANA, or sending a predictive alert to field crews. Another example: grid imbalance events could be streamed into Event Mesh, where AI models forecast demand spikes and automatically adjust load‑balancing workflows in BTP.

Re: Event‑driven architecture

henry-collins1 — Mon, 06 Jul 2026 22:14:34 GMT

A good approach is to keep Event Mesh focused on reliable event routing and let AI services handle the intelligence layer. Use clear event schemas, avoid sending unnecessary data, and make sure AI decisions are traceable before triggering business actions in S/4HANA. For large-scale utility scenarios, monitoring, retry handling, and human approval paths for critical actions are just as important as the AI model itself.

Re: Event‑driven architecture

Atul_Joshi85 — Tue, 07 Jul 2026 17:22:05 GMT

Thanks for the input. My requirement is specifically about large‑scale utility workflows where Event Mesh must do more than just route events — it needs schema governance, replay, and filtering to support AI services at scale.

The answer doesn’t fully explain how Joule or AI Core subscribe to Event Mesh topics, classify millions of meter events, and then trigger SAP Build Process Automation or S/4HANA actions. Without that integration detail, the solution doesn’t meet the operational needs of meter‑to‑cash and outage management in real utility landscapes.

Re: Event‑driven architecture

Atul_Joshi85 — Mon, 20 Jul 2026 15:24:38 GMT

Event‑Driven Architecture (EDA) in SAP is about treating business milestones as first‑class signals, not just technical logs. Instead of waiting for batch jobs, events like sales.order.created or meter.reading.updated flow instantly into SAP Event Mesh or Integration Suite, where they trigger downstream processes.

Key points to keep in mind:

Protocols & Ingestion: Use MQTT for IoT/DER data, AMQP for enterprise queuing, and OData for ERP connectivity.
Resiliency: Always design for retries and dead letter queues (DLQ) so failed events don’t vanish silently.
Governance: Schema registry, correlation IDs, and ownership are non‑negotiable to avoid drift and ensure traceability.
Patterns: Event Sourcing and CQRS help scale state management and auditability.
Business Outcomes: Moving from monthly billing cycles to event‑triggered checks can reduce delinquency by double‑digit percentages and improve customer trust.

In short, EDA is not just a technical choice — it’s the operating model for intelligent enterprises. By combining SAP BTP’s event mesh, AI Core, and Joule automation, you move from reactive batch processing to proactive, real‑time business outcomes.