5. 3. 1. If you're either composing or orchestrating services, people will think you are the source of the produced data. Microservices are more often seen as services that should not participate in complex compositions and rather be more autonomous. Keep in mind that orchestration is a compound pattern that offers several capabilities to create complex compositions of services. The goal of microservices is to increase the velocity of application releases, by decomposing the application into small autonomous services that can be deployed independently. Don't Be a Transformer. Be Clear As Crystal. There is another pattern, called choreography, where services communicate with each other in a publish-subscribe manner via events. Use Known Patterns. This will keep coupling low and remove the need for an intelligent orchestrator. Lots of logic to handle transaction execution needs to be put in orchestrator. Orchestration patterns have the downside that a different service needs to be developed to work as an orchestrator. Orchestrating Microservices: A Guide for Architects. Design patterns for microservices. Rollbacks are easier to manage in orchestration pattern. You can ... 2. 02/25/2019; 2 minutes to read; In this article. Orchestration entails actively controlling all elements and interactions like a conductor directs the musicians of an orchestra, while choreography entails establishing a pattern or routine that microservices follow as the music plays, without requiring supervision and instructions. 4. Be Resilient. Since there many risks to orchestrating microservices, it is prudent for you to limit your orchestration to places that need it. Orchestration pattern is ideal for large and complex microservices system. Keep It Small.