AgentSkillsCN

architecture-microservices

针对独立部署能力、团队自主性以及领域级扩展性，采用微服务架构设计。当需界定系统边界、模块间关系，以及架构层面的约束时，可选用此流程；但若仅对单个模块进行重构且不涉及架构层面的影响，则不宜使用。

SKILL.md
--- frontmatter
name: architecture-microservices
description: "Microservices architecture design for independent deployability, team autonomy, and domain-level scaling. Use when system boundaries, module relationships, and architecture-level constraints are being defined; do not use for single-module implementation refactors without architecture impact."

Architecture Microservices

Trigger Boundary

  • •Use when independent deployment and scaling by domain are explicit goals.
  • •Do not use for single-deploy modular systems; use architecture-monolith.
  • •Do not use solely to evaluate options; use architecture-tradeoff-analysis first when undecided.

Goal

Define robust service boundaries, contracts, and operational controls for microservices.

Shared Architecture Contract (Canonical)

  • •Use skills/architecture-principles/references/architecture-governance-contract.md as the only schema source.
  • •Validate all IDs, lifecycle states, and gate rules against the canonical contract.
  • •Do not define local ID formats or alternate state machines.

Compliance & Governance Baseline (US, Japan, EU)

  • •Define data ownership and residency per service boundary.
  • •Enforce service-to-service authentication, authorization, and audit trails.
  • •Prepare an ARC-CMP-* evidence package for compliance sign-off.

Inputs

  • •Domain decomposition and team ownership model
  • •Scalability and availability targets
  • •Integration patterns and compliance constraints

Outputs

  • •Service boundary map with ownership and dependencies
  • •API and event contract strategy
  • •Resilience and observability requirements per service

Workflow

  1. •Derive service boundaries from domain and team topology.
  2. •Assign ownership and lifecycle responsibility per service.
  3. •Define synchronous and asynchronous contracts explicitly.
  4. •Specify reliability patterns: retries, timeouts, and circuit breaking.
  5. •Record consistency model and data ownership per boundary.

Quality Gates

  • •No ambiguous ownership between services.
  • •Inter-service contracts are versioned and reviewable.
  • •ARC-CMP-* evidence package is complete and approved.
  • •Greenfield designs exclude fallback paths; brownfield rollback requires trigger and runbook.

Failure Handling

  • •Stop when boundaries are split by technical layers instead of domains.
  • •Stop when canonical contract validation fails.
  • •Escalate when critical services lack clear resilience strategy.