Azure App architecture guide is a great place to learn about many architectural styles, and one such style is Event-driven arch.
The guide provides an introduction to the key concepts of event-driven architecture, including event sources, event processors, and event consumers. It also covers the benefits of event-driven architecture, such as improved scalability, increased resiliency, and the ability to respond to changing business requirements.
<Quote from article>
An event-driven architecture can use a publish/subscribe (also called pub/sub) model or an event stream model.
- Pub/sub: The messaging infrastructure keeps track of subscriptions. When an event is published, it sends the event to each subscriber. After an event is received, it cannot be replayed, and new subscribers do not see the event.
- Event streaming: Events are written to a log. Events are strictly ordered (within a partition) and durable. Clients don't subscribe to the stream, instead a client can read from any part of the stream. The client is responsible for advancing its position in the stream. That means a client can join at any time and can replay events.
</Quote from article>
Original Blog here:
Further reading:
