What problem does it solve? Distributed transactions across services are fragile and hard to scale. This Skill provides architectural guidance for replacing them with local transactions plus events, so each step in a distributed process stays independently retryable and compensatable. ## Core Features & Use Cases - Pattern Selection: Choose between Saga (stateless, simple workflows), Process Manager (stateful, complex multi-step decisions), and Choreography (decentralized, no coordinator) based on your workflow shape. - Implementation Checklist: Verify local transaction scope, compensation actions, internal vs external event separation, retry policies, and dead letter queues before shipping. - Anti-Pattern Detection: Identify distributed transactions, missing compensation, synchronous service-to-service calls, fire-and-forget messaging, and god process managers. - Use Case: When building an order fulfillment flow spanning payment, inventory, and shipping services, use this Skill to structure each step as a local transaction with events and defined compensation for failures. ## Quick Start Ask the solution-architect skill to help design a saga for an order workflow that spans payment, inventory, and shipping services.
