-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Event-driven architecture enables systems to share data changes in real time across multiple, decoupled teams. It offers an alternative to the coupled, system-to-system API paradigm.
An Event Bus allows a system to publish a stream of changes to its data. Systems that are interested in those data changes can receive the information in real time and use it to send updates to trigger actions, send updates to Veterans, communicate with other internal teams, and more.
Teams can use the Enterprise Event Bus to generate events based on state changes to the data they own and publish them on an event bus. Consumers are free to consume those events and react accordingly. More specifically, with the Enterprise Event Bus:
- Event producers don’t need to know who the interested consumers are and therefore don’t need to keep growing their outbound complexity.
- Multiple consumers may receive and act on an event; it’s not just an asynchronous queue sitting between a single producer and consumer.
Take the next steps to explore and begin using the Enterprise Event Bus:
- Learn more about which teams would benefit from using event-driven architecture
- Reach out to us with questions.