In microservice or event-driven architectures you might find yourself having to solve issues which are simple when working with monolithic applications. One of these challenges is distributed transactions, i.e., performing an action across multiple services can be safely reversed when something fails along the call chain. The Saga pattern is an established approach to make this happen. Let's have a look at what it is, how we can implement it in a modern Symfony application and when we might want to avoid it.