Gatare Libère
Gatare's Blog

Gatare's Blog

How do microservices collaborate with each other?

Photo by Ferdinand Stöhr on Unsplash

How do microservices collaborate with each other?

Gatare Libère's photo
Gatare Libère
·May 11, 2022·

2 min read

Microservices are an architectural and organizational approach to software development where software is composed of small independent services that communicate over well-defined APIs. These services are owned by small, self-contained teams.

Microservices architectures make applications easier to scale and faster to develop, enabling innovation and accelerating time-to-market for new features.

Microservices have two ways of interacting and collaborating: orchestration and choreography

The diagram below illustrates the collaboration of microservices.

0_-H1oVQkcQD9mtis-.jpeg

Microservices orchestration and choreography interaction diagram Choreography is like having a choreographer set all the rules. Then the dancers on stage (the microservices) interact according to them. Service choreography describes this exchange of messages and the rules by which the microservices interact.

Orchestration is different. The orchestrator acts as a center of authority. It is responsible for invoking and combining the services. It describes the interactions between all the participating services. It is just like a conductor leading the musicians in a musical symphony. The orchestration pattern also includes the transaction management among different services.

The benefits of orchestration:

  1. Reliability — orchestration has built-in transaction management and error handling, while choreography is point-to-point communications and the fault tolerance scenarios are much more complicated.

  2. Scalability — when adding a new service into orchestration, only the orchestrator needs to modify the interaction rules, while in choreography all the interacting services need to be modified.

Some limitations of orchestration:

  1. Performance — all the services talk via a centralized orchestrator, so latency is higher than it is with choreography. Also, the throughput is bound to the capacity of the orchestrator.

  2. Single point of failure — if the orchestrator goes down, no services can talk to each other. To mitigate this, the orchestrator must be highly available.

Real-world use case: Netflix Conductor is a microservice orchestrator and you can read more details on the orchestrator design.

Question — Have you used orchestrator products in production? What are their pros & cons?

 
Share this