Architecture Microservices

Overview

Use this skill to design microservice architectures that trade monolithic simplicity for bounded autonomy intentionally.

Scope Boundaries

• Different domain areas change at different speeds and require independent release cadence.
• Team autonomy and ownership boundaries are blocked by shared code/runtime coupling.
• Operational platform maturity exists to absorb distributed-system overhead.

Core Judgments

• Service boundary: domain capability, data ownership, and team ownership alignment.
• Integration model: synchronous calls, events, or hybrid by invariant type.
• Consistency strategy: local transactions plus saga/compensation where needed.
• Operational budget: observability, incident response, platform engineering capacity.