Microservices Architecture event_driven_arch.txt - rnakidi/dsa GitHub Wiki
Event-driven communication is odd compared to request-response calls.
What’s an event, and what should be inside?
Event-driven architecture (EDA) works differently from the usual request-response model in microservices.
Instead of one service telling another what to do, a microservice emits an Event—a signal that something happened—and other services can decide whether to respond.
But what should be inside the event?
Two main approaches
• Just an Identifier • Fully Detailed Events
Data should flow freely in a well-designed system.
Events should be the carriers of autonomy, not the chains of dependency.