microservices-boundaries SKILL.md skillA
microservices-boundaries from amey-thakur/ai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amey-thakur/ai-skills/microservices-boundaries@git:20260720.67d6135Pins git:20260720.67d6135 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amey-thakur/ai-skills
- Path
skills/architecture/microservices-boundaries/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260720.67d6135, committed Jul 20, 2026
- Size
- 3,738 bytes
- Repository stars
- 14
- License
- MIT
Split services along business capabilities with clear data ownership, avoiding the distributed monolith. Use when decomposing a system into services or diagnosing services that must always deploy together.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Microservices boundaries The hard part of microservices is not building services; it is drawing the lines between them. Wrong boundaries produce a distributed monolith: all the operational cost of microservices with none of the independence, where every change touches three services and they deploy in lockstep. ## Method 1. **Split by business capability, not technical layer.** A service owns a domain (ordering, billing, inventory) end to end, not a tier (there is no "database service" and no "API service"). Bounded contexts from the domain (see domain-driven-design) are the natural seams; org structure will shape them anyway (Conway's law), so design the boundaries and the team boundaries together. 2. **Give each service sole ownership of its data.** One service, one database, no other service reaching into it: services collaborate through APIs and events (see event-driven-architecture), never shared tables. A shared database is the distributed monolith's spine: it couples deploys, schemas, and failures across every service that touches it. 3. **Test boundaries against change and chattiness.** Good …
Read the whole file at its exact version.
How to install
mdr add amey-thakur/ai-skills/microservices-boundaries@sha256:f24cde6ca648f7acThe line at the top of this page pins the label git:20260720.67d6135, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qprykajigdfjy5p3)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 20, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3738 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
amey-thakur/ai-skills · 14 stars · license MIT · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qprykajigdfjy5p3 GET https://markdownregistry.com/api/v1/resolve?ref=amey-thakur/ai-skills/microservices-boundaries GET https://markdownregistry.com/api/v1/blob/f24cde6ca648f7ac636ad254059c53fcf1a95709117b0cbb3cb90da4955d4873
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.