Microservices
Deploy capabilities independently when operational independence justifies coordination.
Open field noteService decomposition
Compare one deployable unit, internal modules, and separate services to balance independent releases with operating complexity.
Search within: Service decomposition
3 field notes
| Concept | Features | Advantages | Limitations | Suitable situations | Combination conditions |
|---|---|---|---|---|---|
| Microservices | Independently deployable capability services | Library can release without rebuilding Billing | Network failures and data coordination | Stable boundaries and independent release needs | Can coexist with a modular monolith |
| Modular monolith | Explicit module APIs within one deployment | Library changes stay behind its API | Boundaries need enforcement; releases stay shared | Clear ownership without remote calls | Can use clean or hexagonal module internals |
| Monolith | One server-side release unit | One release pipeline for a small team | Shared release and process failure boundaries | Closely related capabilities with one team | Can contain layers and explicit modules |