Sagas: As discussed, a saga breaks a long-running transaction into smaller?

transactions, each handled by an individual service. Sagas manage failures by using

compensating actions, thus avoiding the need for distributed locking.