when-NOT-to-use-microservices
when-NOT-to-use-microservices is a System design & architecture decisions skill for AI agents, published by sandeepmvl in the rails-skills repository on GitHub. Skillspace rates when-NOT-to-use-microservices C (73/100) and it passed the safety scan; the rating is based on static analysis only.
A diagnostic skill that refuses microservices in the wrong contexts and recommends a modular monolith instead. Covers the team-size threshold, the deploy-coupling argument, the distributed-systems tax, when DHH's "majestic monolith" is correct, and the "you're not Netflix" rule. Use when the user mentions microservices, splitting our monolith, service-oriented architecture, going micro, "should we split the codebase", or asks how to break up a Rails app. THIS SKILL'S JOB IS TO PUSH BACK before the user spends a year on a migration they will regret.
- Grade
- C
- Quality
- 73 / 100
- Safety
- Passed
- GitHub stars
- 21
Unproven: rated by static analysis only, not yet compared head-to-head.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 97 / 100
- Maturity
- Structured: ships references or scripts
- Security scan
- No issues found
- License
- MIT
- Adoption
- Adopted by 0 other repositories, in 0 collections
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.