What is Event-Driven Architecture?

Event-driven architecture, abbreviated EDA, is a design style in which components communicate by producing and consuming events. Instead of one service explicitly calling another, the producer publishes a fact such as "OrderPlaced" or "StockChanged" to an event broker, and any interested service subscribes to react.

Definition

EDA relies on an event broker, often a message queue or streaming platform such as Kafka, RabbitMQ, or a cloud-native equivalent. Producers and consumers do not know about each other directly; they only share a contract about the event format. New consumers can be added without modifying producers, which lowers the cost of evolving the system.

Why it matters

In commerce, many actions trigger cascading work: an order has to update inventory, notify the warehouse, charge the customer, send a confirmation, and feed analytics. EDA decouples these steps so each can scale and fail independently. It also makes near-real-time integrations across composable services practical, because new capabilities can plug in to existing event streams.

Trade-offs

Eventual consistency replaces synchronous correctness, which forces teams to think about ordering, retries, and idempotency. Observability and tracing become more important than in request-response architectures. The reward is a system that scales horizontally, recovers gracefully from partial failures, and adapts as business processes change.

Related

Explore Composable Headless Frontend · Composable Digital Experience Platform.