Skip to content

Event broker implementation pattern

Event broker implementation pattern refers to the architectural practice of building an Event-driven communication system "from scratch" rather than relying solely on pre-existing, external infrastructure^[100-InBox__Microservices_with_Node_JS_and_React.md].

This pattern is central to specific microservices learning paths, such as the project found in the Microservices-with-Node-JS-and-React/blog repository^[100-InBox__Microservices_with_Node_JS_and_React.md]. In these educational contexts, the implementation focuses on creating a custom broker to handle event communication^[100-InBox__Microservices_with_Node_JS_and_React.md].

In more advanced or production-grade applications, such as the ticketing system in Microservices-with-Node-JS-and-React/ticketing, this custom approach is often superseded or replaced by dedicated streaming servers like NATS Streaming Server^[100-InBox__Microservices_with_Node_JS_and_React.md]. NATS serves as the specific infrastructure facilitating event communication between microservices in that environment^[100-InBox__Microservices_with_Node_JS_and_React.md].

Sources

^[100-InBox__Microservices_with_Node_JS_and_React.md]