How To Orchestrate Event-Driven Microservices
Too Long; Didn't Read
In the previous post in this series, we learned about the pitfalls of tightly coupled direct call microservices and how to avoid them by implementing the choreographed event-driven microservices pattern. Instead of API calls, microservices publish records of their doings, also known as events. The Orchestration pattern involves a central orchestration service (or services) which issues commands to and awaits responses from worker microservices. By removing this tight coupling between services, it's possible to reap the benefits offered by the microservices architecture pattern.