Hands-On Software Architecture with Golang

The compensating-transaction pattern

A question arises in such a scenario, let's say the services want to have some sort of transactional semantics—either all the services finish successfully or none do. To keep things simple, let's assume that isolation (simultaneous operations not seeing intermediate state) is not required. This is a common use case for complex workflows (say, the fulfillment of booking on our travel website), where multiple actions need to happen with a possible modification of different data stores. In such scenarios, providing strong consistency semantics will not be scalable due to the distributed nature of the environment and contention due to the scale, and hence the architecture follows the async pattern. With this ...