Coordinate distributed transactions across microservices using Saga patterns.
npx skills add https://github.com/mthang1801/go-domain-driven-design --skill saga
Please help me install this Agent Skill. Skill: saga Source: https://github.com/mthang1801/go-domain-driven-design/tree/main/.claude/skills/saga Command: npx skills add https://github.com/mthang1801/go-domain-driven-design --skill saga
Coordinating distributed transactions across microservices can be fragile without a formal orchestration pattern. This Skill provides a structured approach to implementing Saga-based workflows using the core abstractions SagaDefinition, SagaStep, and SagaManager, including idempotency, compensation, and strict reply header contracts.
Create and run a basic OrderPlacementSaga using the example files to validate the end-to-end flow.
High-intent search queries and answers about installing and using this skill.
Distributed transactions are orchestrated by defining deterministic sequences of remote steps using SagaDefinition and SagaStep, ensuring eventual consistency across services with explicit compensation handling and idempotent workflows.
Compensating actions in a Kafka-based distributed workflow are handled by enforcing strict reply header contracts for routing, allowing the SagaManager to execute explicit rollback steps and achieve eventual consistency across microservices.
Idempotency in DDD saga orchestration is managed through header-driven routing and Kafka-based messaging, ensuring that remote command invocations and compensating actions can be safely retried without duplicate side effects.
Yes, this approach supports long-running workflows by utilizing Saga core abstractions like SagaManager and SagaStep, integrating Kafka-based messaging to coordinate distributed flows and remote command invocations across microservices.
Yes, SagaDefinition and SagaStep are required core abstractions for coordinating distributed transactions, providing deterministic sequencing and explicit compensation handling to maintain eventual consistency across services.
Saga orchestration may be unsuitable if your distributed transactions require strict ACID guarantees rather than eventual consistency, or if your microservices architecture lacks Kafka-based messaging and strict reply header contracts.
giuseppe-trisciuoglioImplement choreography and orchestration sagas for Spring Boot microservices.
ChrstprJohnCoordinate distributed transactions across microservices using the Saga pattern with compensating actions and rollback on failure.
StudentCristianCoordinate event sourcing, CQRS, and saga patterns for resilient event-driven architectures.
ccfCoordinate distributed transactions across services using saga patterns.
