Skip to content

Microservices Event-driven communication

Event-driven communication is a messaging pattern used in [[Microservices]] architectures where services interact by producing and consuming events rather than making direct synchronous calls (e.g., REST/HTTP).^[100-InBox__Microservices_with_Node_JS_and_React.md]

In an event-driven architecture, services are decoupled; the producer emits an event without needing to know which specific services will consume it or how they will process it.^[100-InBox__Microservices_with_Node_JS_and_React.md] This pattern is typically facilitated by an event broker or message bus, which handles the routing of events from the source to the interested listeners.^[100-InBox__Microservices_with_Node_JS_and_React.md]

A common tool for implementing this type of communication in Node.js environments is NATS Streaming Server, which provides the infrastructure for reliable event passing between services.^[100-InBox__Microservices_with_Node_JS_and_React.md]

Implementation Example

The ticketing project demonstrates this approach by using NATS Streaming Server to manage event communication between different microservices in an e-commerce application.^[100-InBox__Microservices_with_Node_JS_and_React.md]

Sources

^[100-InBox__Microservices_with_Node_JS_and_React.md]