spring-boot-saga-pattern

SKILL.md

Distributed transaction management across microservices using choreography or orchestration patterns.

Supports two saga approaches: choreography-based (event-driven, decoupled) and orchestration-based (centralized coordinator with easier tracking)

Requires compensating transactions for every forward operation to ensure rollback capability and eventual consistency

Integrates with Spring Boot 3.x, Kafka, RabbitMQ, and frameworks like Axon Framework, Eventuate Tram, and Camunda

Emphasizes idempotent operations, persistent saga state, timeout handling, and dead-letter queues for failure scenarios

Includes monitoring, distributed tracing, and testing strategies for complex multi-service workflows

Spring Boot Saga Pattern

Overview

Implements distributed transactions across microservices using the Saga Pattern. Replaces two-phase commit with a sequence of local transactions and compensating actions. Supports choreography (event-driven) and orchestration (centralized coordinator) approaches with Kafka, RabbitMQ, or Axon Framework.

When to Use

Building distributed transactions across multiple microservices

Replacing two-phase commit (2PC) with a more scalable solution

Handling transaction rollback when a service fails

Ensuring eventual consistency in microservices architecture

Implementing compensating transactions for failed operations

Coordinating complex business processes spanning multiple services

Trigger phrases: distributed transactions, saga pattern, compensating transactions, microservices transaction, eventual consistency, rollback across services, orchestration pattern, choreography pattern

Instructions