// RULES
Microservice rules Best practices for microservices, one rule per page: why it matters, how to apply it and an example. They are grouped into checklists you can apply to a service.
All categories Ownership API Events Data Resilience Observability Security Deployment Decisions Architecture All priorities Critical High Medium Low 1 rule of 70 · Clear filters
Decisions Key decisions are recorded At least one architecture decision is written down and accepted, with its context and consequences.
Low Checked automatically
Check your own service against these rules Describe a service in MICROSERVICE.md™ and apply a checklist: the rules marked "checked automatically" are evaluated against the design, and each failing one points to where to fix it.
// stay in the loop
Product updates, tips, and new features.
⬡ MICROSERVICE.md™ The open spec for AI-ready microservice documentation.
Product
Resources
For AI agents
Company