Microservices

Workflow

1. First establish an independent deployment or ownership need. Compare against a modular monolith and identify migration cost.
2. Specify service contracts, data ownership, timeouts, retries, idempotency and degraded behavior.
3. Avoid shared mutable databases and synchronous call chains where a local boundary would suffice.
4. Plan observability, compatibility, rollback and operational responsibility before extraction. Verify one end-to-end scenario.

Completion

Return the concrete result, verification evidence and any material unresolved limitation. Keep documentation proportional to the change and preserve human feedback.

Focused references

• Detailed examples: load only the section relevant to the task.

---

Canonical source: skills/architecture/microservices.md.