Course contentsShow
← Cloud and Infrastructure
Lesson 2587 of 2,98955. Microservices on CloudFree lesson

Compensating Transactions

Understand how to implement compensating transactions to rollback changes when distributed operations fail.

Compensating Transactions

What You'll Learn

You'll learn how to undo changes in distributed microservices when an operation fails midway, ensuring data consistency without traditional database rollback.


The Core Problem

In traditional monolithic systems, if an operation fails, you roll back the entire database transaction. But in microservices, you often have multiple services—each with its own database—participating in a business operation. If step 3 of a 5-step process fails, you can't just "rollback" the independent databases in services 1 and 2.

What Is a Compensating Transaction?

A compensating transaction is a specific action that reverses the effect of a previously completed operation. Think of it like the "undo" button in a text editor—it doesn't magically rewind time, but it applies a deliberate action that negates the previous change.

Analogy: Imagine booking a vacation. You reserve a flight (Service A), then a hotel (Service B), then a rental car (Service C). If the car reservation fails, you can't "rollback" the flight and hotel databases. Instead, you explicitly cancel the flight and hotel—those cancellations are compensating transactions.

How It Works

When implementing the Saga Pattern, each forward transaction has a corresponding compensating transaction defined:

  • Order Service creates order → Compensating: cancel order
  • Payment Service charges card → Compensating: refund card
  • Inventory Service reserves stock → Compensating: release reservation

If any step fails, the saga orchestrator triggers compensating transactions in reverse order to undo completed work.

Key Design Principles

  • Compensating transactions must be idempotent (safe to retry)
  • They should handle partial failures gracefully
  • Log all compensations for audit trails
  • Design them alongside forward transactions, not as an afterthought

Key Takeaway: Compensating transactions provide explicit "undo" logic for distributed operations, maintaining eventual consistency across microservices when failures occur by reversing completed steps in a controlled manner.