Event-driven architecture

Event driven architecture is about the flow of a program or solution. These can be from monolithic solutions to distributed services. The key part is that events are used to represent important changes in state across service boundaries. and is not necessarily used to store state like Event sourcing.

These events are data-contracts between these service boundaries.

PubSubs and other message brokers are great examples of event-driven architecture.

Reference

Wierik, M. te. (2022, November 14). Event sourcing versus event-driven architecture. Geek Culture. https://medium.com/geekculture/event-sourcing-versus-event-driven-architecture-753aa5a5d0f6

Highlights or timestamps

Event Sourcing Versus Event-Driven Architecture

Event-driven architecture uses events to communicate notable data changes between service boundaries. Like the event sourcing pattern, the events represent a noteworthy change in state. Within event-driven architecture, the event is used as a data contract to communicate the information. The publisher and the consumer must have a common understanding of the message that gets shared. Otherwise, the message may be misinterpreted, and the information communicated will be incomplete.

— ^bef2b2 from Event Sourcing Versus Event-Driven Architecture