Orchestration coordinates tasks by directing when other services act. In a layered application, it belongs in the Application Layer, where it coordinates work without absorbing business rules or HTTP and database concerns. section 4.7.4
In distributed systems, synchronous orchestration has a tradeoff: a central service can direct a sequence of actions, but services must be available at the same time. A delay or failure can topple the chain. Choreography offers a different approach, with services reacting independently to events. section 7.1
Figure 7.1 The Distributed Monolith: When services are coupled in time, a failure at the bottom of the chain topples everything above it.

The domino-chain diagram illustrates how a failure in one service can affect the rest of a synchronously coupled system. section 7.1


















