Event-Driven Microservices Architecture (MSA)
An Event-Driven Microservices Architecture (MSA) is an MSA where microservices communicate with each other through the exchange of events (rather than through traditional request-response calls).
- See: Data-Layer MSA.
References
2023
- chat.openai.com
- Q: what is an Event-Driven microservices architecture?
- A: An event-driven microservices architecture is a design pattern for building software systems that use events as a fundamental means of communication between microservices. In this architecture, microservices are designed to communicate with each other through the exchange of events, rather than through traditional request-response calls.
Here's how it works: When a microservice performs a task that affects another microservice, it sends an event to a message broker. The message broker is responsible for delivering the event to the other microservice, which can then perform the necessary actions in response to the event.
One of the main benefits of an event-driven architecture is that it allows microservices to be decoupled from one another. This means that microservices can evolve and change independently, without affecting the other microservices in the system. It also makes it easier to scale the system, since new microservices can be added or removed without affecting the existing ones.
Overall, an event-driven microservices architecture can help you build more flexible, scalable, and resilient software systems.
2021
- https://medium.com/swlh/microservices-databases-b4cb949d0544
- QUOTE: ... In Event-Driven architectures, microservices publish events (producers) and/or subscribe to topics (consumers). They do not care who consumes the events it produces and who produced the events it consumes. ...
... The event-driven approach solves the problem of sharing data between contexts. Yet, the event format is not standardized. Producers must share the events schema before the consumer be able to consume them. Then, the consumer still needs to transform the event from the original schema to its data domain. ...
- QUOTE: ... In Event-Driven architectures, microservices publish events (producers) and/or subscribe to topics (consumers). They do not care who consumes the events it produces and who produced the events it consumes. ...
