skills.rest
erikshafer
erikshaferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

distributed-saga-considerations

Design distributed sagas with choreography, orchestration, compensating actions, and idempotence.

Updated Apr 21, 2026
Search Tags:#orchestration#distributed systems#choreography#failure handling#saga design
One-click install
npx skills add https://github.com/erikshafer/CritterCab --skill distributed-saga-considerations
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-saga-considerations
Source: https://github.com/erikshafer/CritterCab/tree/main/docs/skills/distributed-saga-considerations
Command: npx skills add https://github.com/erikshafer/CritterCab --skill distributed-saga-considerations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Wolverine, Marten, Polecat, Aspire, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides in-depth guidance for designing and implementing distributed sagas in CritterCab, addressing common challenges in distributed systems coordination and ensuring reliable system behavior.

Core Features & Use Cases

  • Distributed Saga Design: Offers design principles for distributed systems using sagas in CritterCab, focusing on choreography vs. orchestration, compensating actions, and idempotence.
  • Use Case: When developing a ride-sharing platform and need to handle workflows like trip completion, payment processing, and rider onboarding across multiple bounded contexts.
  • Use Case: Diagnosing and resolving wedged sagas or analyzing failure modes in production systems.

Quick Start

Review the "TripCompletionSaga" design in CritterCab to understand saga orchestration and failure handling.

Frequently Asked Questions about distributed-saga-considerations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are compensating actions in distributed saga design?▼

Compensating actions in distributed saga design undo or neutralize previously completed steps when a workflow fails, ensuring system consistency across bounded contexts without distributed transactions.

How do I choose between choreography and orchestration for distributed sagas?▼

Choosing between choreography and orchestration for distributed sagas depends on workflow complexity; choreography decentralizes event-driven reactions, while orchestration centralizes control for complex multi-step processes like trip completion.

How do I handle idempotence and failure modes in distributed systems?▼

Handling idempotence and failure modes in distributed systems requires designing sagas to safely process duplicate messages and diagnosing wedged sagas to maintain reliable system behavior.

Do I need Wolverine to implement distributed sagas?▼

You need Wolverine and related libraries to implement distributed sagas, as they provide the necessary messaging infrastructure and saga persistence mechanisms for complex workflows across bounded contexts.

How do I diagnose a wedged saga in production distributed systems?▼

Diagnosing a wedged saga in production distributed systems involves analyzing failure modes within the saga design, checking compensating actions, and tracing message flows across bounded contexts to resolve stuck workflows.

Related Skills

Explore More Software Engineering Skills→
erikshafererikshafer

wolverine-sagas

Manage long-running workflows in CritterCab using Wolverine sagas.

Community
Advanced
jonathanbelolojonathanbelolo

composable-rust-sagas

Implement distributed sagas in Rust with CQRS/Event Sourcing and compensation.

Community
Advanced
erikshafererikshafer

service-bootstrap

Configures CritterCab services with Wolverine, Marten/Polecat, and Aspire integration.

Community
Advanced
SaiyedMuhammadAnasMaududiSaiyedMuhammadAnasMaududi

saga-orchestration

Coordinate distributed transactions across microservices using Saga patterns.

Community
Advanced