Choosing your coordination approach

Choreography and orchestration both have their uses when integrating microservices. Choose choreography within the boundary of a single microservice, where you have full control over dependencies. Choose orchestration when you work across microservice boundaries. For example, multiple microservices that participate in a distributed transaction will benefit from orchestration to account for rollback from failures. Microservices that handle events that might be of interest to other microservices will benefit from choreography and an event-driven architecture.

A common pattern for implementing rollback when multiple systems are involved in a single transaction is the saga pattern. For more information, see Saga pattern in the guide Enabling data persistence in microservices.