architecture

To choose a microservices architecture pattern, evaluate cross-service pressures like data ownership and integration seams. This Skill selects a primary pattern, such as Saga or CQRS, plus supporting patterns to address your specific reliability and consistency challenges.

You need Saga or CQRS patterns for distributed systems when work spans multiple services requiring eventual consistency or clearer domain boundaries. This Skill applies when you face integration seam challenges across teams, not for single-process code structure.

The best way to refactor cross-service architecture is to document criteria and select a primary pattern with up to two supporting patterns. This Skill provides an implementation plan with guardrails and metrics alignment for migrating between event-driven and request/response models.

No, you cannot use this Skill for single service call timeouts or retries. It is designed specifically for multi-service boundaries addressing domain boundaries, data ownership, and integration seams, rather than in-process code structure or single-call resilience.

To plan a migration to a new system pattern, describe your cross-service pressure concisely. The Skill outputs a high-level implementation plan with guardrails and documented criteria, recommending one primary pattern and up to two supporting patterns for the refactor.

Yes, this Skill helps with API gateway and domain boundary design by selecting appropriate system patterns. It addresses integration seams and data ownership across multi-service boundaries, determining the most suitable pattern for your specific cross-service pressures.