Agent skill

Spring Boot Saga Pattern

by giuseppe-trisciuoglio in giuseppe-trisciuoglio/developer-kit

Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices.

MITAuto-check: notesBackend & APIs

Install Spring Boot Saga Pattern

skills CLI
$ npx skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-saga-pattern -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install giuseppe-trisciuoglio/developer-kit spring-boot-saga-pattern --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/developer-kit-java/skills/spring-boot-saga-pattern .claude/skills/spring-boot-saga-pattern && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spring-boot-saga-pattern
GitHub stars
357
Token cost
~2.5k tokens
SKILL.md length
455 words
Files
12 (incl. references)
Skills in repo
115
Repo updated
First seen
Licence
MIT

At a glance

Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices.

  • Works in 8 steps: Design Transaction Flow → Choose Implementation Approach → Implement Services with Local Transactions → …
  • Implementing distributed transactions across services
  • SKILL.md covers Overview, When to Use, Instructions and Best Practices, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spring Boot Saga Pattern is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices. Use when implementing distributed transactions across services, handling compensating transactions, ensuring eventual consistency, or building choreography or orchestration-based sagas with Kafka, RabbitMQ, or Axon Framework.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/choreography-implementation.md`, `references/compensating-transactions.md` and `references/error-handling-retry.md`).

It sits in Backend & APIs, covering Microservices, Event-driven systems and Backend development. It works with Spring Boot and Apache Kafka. The repository describes itself as: Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI. The licence is MIT.

When your agent uses it

  • Implementing distributed transactions across services
  • Handling compensating transactions
  • Ensuring eventual consistency
  • Building choreography

Example prompts

  • “Use the spring-boot-saga-pattern skill to provide distributed transaction patterns using the Saga Pattern for Spring Boot microservices”
  • “/spring-boot-saga-pattern”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Design Transaction Flow
  2. Choose Implementation Approach
  3. Implement Services with Local Transactions
  4. Implement Compensating Transactions
  5. Set Up Message Broker
  6. Implement Saga Orchestrator (Orchestration Only)
  7. Implement Event Handlers (Choreography Only)
  8. Add Monitoring and Observability

What it can do on your machine

Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are java).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spring Boot Saga Pattern loads about 2.5k tokens when it runs, and up to ~37k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 455 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~37k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 455 words, ~2,528 tokens.

Download SKILL.mdSave it as .claude/skills/spring-boot-saga-pattern/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
spring-boot-saga-pattern
description
Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices. Use when implementing distributed transactions across services, handling compensating transactions, ensuring eventual consistency, or building choreography or orchestration-based sagas with Kafka, RabbitMQ, or Axon Framework.
allowed-tools
Read, Write, Edit, Bash, Glob, Grep

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

1. Design Transaction Flow

Map the sequence of operations and their compensating transactions:

Order → Payment → Inventory → Shipment
  ↓        ↓        ↓          ↓
Cancel  Refund   Release    Cancel

Validation: Verify every forward step has a corresponding compensation.

2. Choose Implementation Approach
ApproachUse CaseStack
ChoreographyGreenfield, few participantsSpring Cloud Stream + Kafka/RabbitMQ
OrchestrationComplex workflows, brownfieldAxon Framework, Eventuate Tram, Camunda

Validation: Review team expertise and system complexity before choosing.

3. Implement Services with Local Transactions

Each service completes its local ACID transaction atomically:

java
@Service
@RequiredArgsConstructor
public class OrderService {
    private final OrderRepository orderRepository;
    private final KafkaTemplate<String, Object> kafka;

    @Transactional
    public Order createOrder(CreateOrderCommand cmd) {
        Order order = orderRepository.save(new Order(cmd.orderId(), cmd.items()));
        kafka.send("order.created", new OrderCreatedEvent(order.getId(), order.getItems()));
        return order;
    }
}

Validation: Test that local transaction commits before event is published.

4. Implement Compensating Transactions

Every forward operation requires an idempotent compensation:

java
@Service
@RequiredArgsConstructor
public class PaymentService {
    private final PaymentRepository paymentRepository;
    private final KafkaTemplate<String, Object> kafka;

    public void processPayment(PaymentRequest request) {
        Payment payment = paymentRepository.save(new Payment(request.orderId(), request.amount()));
        kafka.send("payment.processed", new PaymentProcessedEvent(payment.getId(), request.orderId()));
    }

    @Transactional
    public void refundPayment(String paymentId) {
        paymentRepository.findById(paymentId)
            .ifPresent(p -> {
                p.setStatus(REFUNDED);
                paymentRepository.save(p);
                kafka.send("payment.refunded", new PaymentRefundedEvent(paymentId));
            });
    }
}

Validation: Confirm compensation can execute safely multiple times (idempotency).

5. Set Up Message Broker

Configure Kafka with idempotent consumers:

java
@Configuration
@EnableKafka
public class KafkaConfig {
    @Bean
    public ConcurrentKafkaListenerContainerFactory<String, Object> kafkaListenerContainerFactory(
            ConsumerFactory<String, Object> consumerFactory) {
        ConcurrentKafkaListenerContainerFactory<String, Object> factory =
            new ConcurrentKafkaListenerContainerFactory<>();
        factory.setConsumerFactory(consumerFactory);
        factory.setCommonErrorHandler(new DefaultErrorHandler());
        return factory;
    }
}

Validation: Enable transactional ID and verify exactly-once semantics.

6. Implement Saga Orchestrator (Orchestration Only)
java
@Service
@RequiredArgsConstructor
public class OrderSagaOrchestrator {
    private final KafkaTemplate<String, Object> kafka;
    private final SagaStateRepository sagaStateRepo;

    public void startSaga(OrderRequest request) {
        String sagaId = UUID.randomUUID().toString();
        sagaStateRepo.save(new SagaState(sagaId, STARTED, LocalDateTime.now()));
        kafka.send("saga.order.start", new StartOrderSagaCommand(sagaId, request));
    }

    @KafkaListener(topics = "payment.failed")
    public void handlePaymentFailed(PaymentFailedEvent event) {
        kafka.send("order.compensate", new CompensateOrderCommand(event.getSagaId()));
        kafka.send("inventory.compensate", new ReleaseInventoryCommand(event.getSagaId()));
        sagaStateRepo.updateStatus(event.getSagaId(), FAILED);
    }
}

Validation: Verify saga state persists before sending commands. Check compensation triggers on each failure path.

7. Implement Event Handlers (Choreography Only)
java
@Service
public class OrderEventHandler {
    private final OrderService orderService;
    private final KafkaTemplate<String, Object> kafka;

    @KafkaListener(topics = "payment.processed", groupId = "order-service")
    public void onPaymentProcessed(PaymentProcessedEvent event) {
        try {
            InventoryReservedEvent result = orderService.reserveInventory(event.toInventoryRequest());
            kafka.send("inventory.reserved", result);
        } catch (InsufficientInventoryException e) {
            kafka.send("inventory.insufficient", new InsufficientInventoryEvent(event.getOrderId(), event.getPaymentId()));
        }
    }
}

Validation: Test that each event handler correctly triggers the next step or compensation.

Show full SKILL.md (193 more words)Show less
8. Add Monitoring and Observability
java
@Configuration
public class SagaMetricsConfig {
    @Bean
    public MeterRegistry meterRegistry() {
        return new PrometheusMeterRegistry(PrometheusConfig.DEFAULT);
    }
}

Track: saga execution duration, compensation count, failure rate, stuck sagas.

Validation: Set up alerts for sagas exceeding expected duration.

Best Practices

Design:

  • Make compensating transactions idempotent using database constraints or deduplication tables
  • Use immutable events (Java records) to prevent accidental mutation
  • Store saga state in persistent storage for recovery

Error Handling:

  • Implement circuit breakers for inter-service calls
  • Use dead-letter queues for messages exceeding retry limits
  • Set appropriate timeouts per saga step (30s default, configurable)

Monitoring:

  • Track saga status: PENDING, COMPLETED, COMPENSATING, FAILED
  • Monitor compensation execution time
  • Alert when sagas exceed SLA duration

Constraints and Warnings

  • Every forward transaction MUST have a corresponding compensating transaction
  • Compensating transactions MUST be idempotent to handle retry scenarios
  • Saga state MUST be persisted to handle failures and recovery
  • Never use synchronous communication between saga participants
  • Sagas provide eventual consistency, not strong consistency
  • Test all failure scenarios including partial failures
  • Consider Axon Framework or Eventuate for complex orchestrations
  • Ensure message brokers are highly available

Examples

Choreography-Based Saga
java
// Application.java
@SpringBootApplication
@EnableKafka
@EnableKafkaListeners
public class OrderApplication {
    public static void main(String[] args) {
        SpringApplication.run(OrderApplication.class, args);
    }
}

// Event Classes (immutable)
public record OrderCreatedEvent(String orderId, List<OrderItem> items) {}
public record PaymentProcessedEvent(String paymentId, String orderId) {}
public record InventoryReservedEvent(String reservationId, String orderId) {}
public record PaymentFailedEvent(String orderId, String reason) {}
public record InsufficientInventoryEvent(String orderId, String paymentId) {}

// OrderService with compensation
@Service
@RequiredArgsConstructor
public class OrderService {
    private final OrderRepository orderRepository;
    private final KafkaTemplate<String, Object> kafka;

    @KafkaListener(topics = "payment.failed", groupId = "order-service")
    public void handleCompensation(PaymentFailedEvent event) {
        orderRepository.findByOrderId(event.orderId())
            .ifPresent(order -> {
                order.setStatus(CANCELLED);
                orderRepository.save(order);
            });
    }
}
Orchestration-Based Saga with Axon Framework
java
// Command
@Aggregate
public class OrderAggregate {
    @AggregateIdentifier
    private String orderId;

    @CommandHandler
    public OrderAggregate(CreateOrderCommand cmd) {
        apply(new OrderCreatedEvent(cmd.orderId(), cmd.items()));
    }

    @EventSourcingHandler
    public void on(OrderCreatedEvent event) {
        this.orderId = event.orderId();
    }

    @CommandHandler
    public void handle(CancelOrderCommand cmd) {
        apply(new OrderCancelledEvent(cmd.orderId(), cmd.reason()));
    }
}

References

© giuseppe-trisciuoglio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in plugins/developer-kit-java/skills/spring-boot-saga-pattern of giuseppe-trisciuoglio/developer-kit.

  • SKILL.md
  • references/choreography-implementation.md
  • references/compensating-transactions.md
  • references/error-handling-retry.md
  • references/event-driven-architecture.md
  • references/examples.md
  • references/orchestration-implementation.md
  • references/pitfalls-solutions.md
  • references/reference.md
  • references/saga-pattern-definition.md
  • references/state-management.md
  • references/testing-strategies.md

Open the folder on GitHubat commit fe73fb3

Compare with similar skills

Spring Boot Saga Pattern next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spring Boot Saga Pattern compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spring Boot Saga Pattern this skillgiuseppe-trisciuoglio/developer-kit357—~2.5kAutomated safety check: NotesMIT
Event Driven Messagingrrezartprebreza/spring-boot-skills301—~556Automated safety check: PassMIT
Event Driven Messagingrrezartprebreza/spring-boot-skills301—~657Automated safety check: PassMIT
Kafka ConfigurationAmplicode/spring-skills128—~4kAutomated safety check: PassNone
Deepstream SopNVIDIA/skills3.6k—~4.7kAutomated safety check: NotesApache-2.0
314 Frameworks Spring Kafkajabrena/plinth447—~561Automated safety check: PassApache-2.0

Similar skills

  • Event Driven Messaging

    rrezartprebreza/spring-boot-skills

    A skill your agent uses when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 3.

    301 GitHub stars~556 tokensUpdated 19 days ago
    Backend & APIsAuto-check passed
  • Event Driven Messaging

    rrezartprebreza/spring-boot-skills

    A skill your agent uses when implementing Kafka, RabbitMQ, Pulsar, or JMS producers and consumers in Spring Boot 4.

    301 GitHub stars~657 tokensUpdated 19 days ago
    Backend & APIsAuto-check passed
  • Kafka Configuration

    Amplicode/spring-skills

    Configures Spring Boot's Kafka starter through application.properties / application.yml.

    128 GitHub stars~4k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Deepstream Sop

    NVIDIA/skills

    Official

    A skill your agent uses when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether…

    3.6k GitHub stars~4.7k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • A skill your agent uses when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory…

    447 GitHub stars~561 tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • A skill your agent uses when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting…

    447 GitHub stars~1.2k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed

More from giuseppe-trisciuoglio/developer-kit

All 115 skills in this repo
  • Nestjs Drizzle Crud Generator

    giuseppe-trisciuoglio/developer-kit

    Generates complete CRUD modules for NestJS applications with Drizzle ORM.

    357 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Actuator

    giuseppe-trisciuoglio/developer-kit

    Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services.

    357 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Crud Patterns

    giuseppe-trisciuoglio/developer-kit

    Provides and generates complete CRUD workflows for Spring Boot 3 services.

    357 GitHub stars~2.5k tokensUpdated 1 mo ago
    Auto-check: notes
  • Spring Boot Security JWT

    giuseppe-trisciuoglio/developer-kit

    Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based…

    357 GitHub stars~3.9k tokensUpdated 1 mo ago
    Auto-check: notes
  • AWS CLI Beast

    giuseppe-trisciuoglio/developer-kit

    Provides advanced AWS CLI patterns for managing EC2, Lambda, S3, DynamoDB, RDS, VPC, IAM, and CloudWatch.

    357 GitHub stars~1.7k tokensUpdated 1 mo ago
    Auto-check: notes
  • PR Review Comments

    giuseppe-trisciuoglio/developer-kit

    Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line.

    357 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check: notes

Categories

Questions about Spring Boot Saga Pattern

What does Spring Boot Saga Pattern do?

Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices. Spring Boot Saga Pattern is an agent skill from giuseppe-trisciuoglio/developer-kit. Provides distributed transaction patterns using the Saga Pattern for Spring Boot microservices.

When should I use Spring Boot Saga Pattern?

Spring Boot Saga Pattern fits situations like: implementing distributed transactions across services; handling compensating transactions; ensuring eventual consistency; building choreography.

How do I install Spring Boot Saga Pattern in Claude Code?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-saga-pattern -a claude-code`. Or copy the skill folder (plugins/developer-kit-java/skills/spring-boot-saga-pattern in giuseppe-trisciuoglio/developer-kit) into .claude/skills/spring-boot-saga-pattern in your project. Claude Code loads it when a task matches its description.

How do I install Spring Boot Saga Pattern in Codex?

Run `npx skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-saga-pattern -a codex`. Or copy the skill folder (plugins/developer-kit-java/skills/spring-boot-saga-pattern in giuseppe-trisciuoglio/developer-kit) into .agents/skills/spring-boot-saga-pattern in your project. Codex loads it when a task matches its description.

Can I use Spring Boot Saga Pattern in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add giuseppe-trisciuoglio/developer-kit --skill spring-boot-saga-pattern -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spring-boot-saga-pattern, .gemini/skills/spring-boot-saga-pattern, .github/skills/spring-boot-saga-pattern and .opencode/skills/spring-boot-saga-pattern in your project.

What does Spring Boot Saga Pattern need to run?

SKILL.md names no scripts, command-line tools or credentials: Spring Boot Saga Pattern is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep.

Does Spring Boot Saga Pattern access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spring Boot Saga Pattern safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Spring Boot Saga Pattern use?

Spring Boot Saga Pattern is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spring Boot Saga Pattern use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 35k tokens, read only when the agent opens those files.

What are the alternatives to Spring Boot Saga Pattern?

Skills that share tags, products or a category with Spring Boot Saga Pattern: Event Driven Messaging (rrezartprebreza/spring-boot-skills, 301 stars), Event Driven Messaging (rrezartprebreza/spring-boot-skills, 301 stars), Kafka Configuration (Amplicode/spring-skills, 128 stars) and Deepstream Sop (NVIDIA/skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spring Boot Saga Pattern?

giuseppe-trisciuoglio (a GitHub user) maintains it in giuseppe-trisciuoglio/developer-kit, which has 357 GitHub stars. The repository holds 115 skills in this directory. The repository was last updated on September 10, 2026.

Source: giuseppe-trisciuoglio/developer-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.