Event-Driven Architecture (EDA)
Quick answer
A model where systems react to events (new order, stock change) in real time, instead of polling periodically.
Key takeaways
- Real-time reaction (push, not poll)
- Decoupling between producers and consumers
- Scalability and resilience
What event-driven architecture is
Event-driven architecture (EDA) is a model where components communicate via events: when something happens (order placed, stock low, delivery confirmed), an event is emitted and consumers react immediately.
Why it matters to the board
EDA brings real-time freshness where it counts: stock updates across channels in seconds, orders route instantly, marketplace cancellations drop. It's the opposite of overnight syncs.
Characteristics
- Real-time reaction (push, not poll)
- Decoupling between producers and consumers
- Scalability and resilience
How CRMconnect helps
CRMconnect uses event-driven flows (webhooks, event queues) for time-sensitive data - stock, orders, statuses - and batch for high volumes, choosing the right model per data type.
Real-world example
A retailer synced stock once overnight, generating unfulfillable orders. Moving to real-time events through CRMconnect cut out-of-stock cancellations from 3.8% to 0.3%.
Last updated:
Frequently asked
Does event-driven mean everything in real time?+
No. It's ideal for time-sensitive data; for high volumes (catalogues, reports) batch stays more efficient. Mature systems combine both.
How does it relate to webhooks?+
Webhooks are a concrete way to deliver events between systems over HTTP - a typical mechanism of event-driven architecture.
Where CRMconnect fits
Related terms
Webhook
HTTP push notification sent automatically on event - the opposite of "polling".
TechnologyReal-time vs batch syncing
The two ways of moving data between systems: instantly on each event, or grouped at scheduled intervals.
OperationsOrder orchestration
Automatically coordinating each order's lifecycle from capture to delivery, across channels and warehouses.
TechnologyMicroservices
A software architecture style where the application is built from small, independent services communicating via API.