Event-driven architecture
Published Updated
What is Event-driven architecture?
An app design in which parts of the system announce events and other parts react to those announcements.
An event records something that happened, such as an order being paid. For example, checkout publishes order-paid and separate handlers send the receipt and update inventory. Those steps can finish at different times, so the interface may need to show progress. Delivery failures, duplicates, and ordering need explicit handling.
When you would use it
Use it when several workflows should respond independently to changes and can tolerate completing at different times.
Common operations
- Define events with stable identifiers.
- Track delivery failures and progress across handlers.