Microservices
Independently deployable services, each owning its own data — trades operational complexity for team/deploy independence.
Why we need this / what value this brings
Lets teams and services scale, deploy, and fail independently — the payoff only shows up once a single team/deploy pipeline is genuinely a bottleneck.
When to use this
When deploy frequency conflicts between teams, or one component needs to scale independently of the rest — not by default.
How to use or implement this
Extract one service at a time from a working modular monolith, starting with the component that has the clearest boundary and the least shared state.
Research questions
- What's the actual trigger point for splitting a monolith into services (team size? deploy frequency conflicts? scaling one part independently)?
Empty folder — drop notes, links, and findings here as you research.