In a distributed system, an application typically needs to call multiple microservices to complete one business transaction. 

To avoid latency issues or two-phase commit problems, you can group your microservices based on transactions.

 This pattern is appropriate if you consider response times important and your different modules do not create a monolith after you package them. 

The following table provides the advantages and disadvantages of using this pattern.

https://docs.aws.amazon.com/prescriptive-guidance/latest/modernization-decomposing-monoliths/decompose-transactions.html