Microservices
Service Ownership Boundaries in Microservices
Service ownership boundaries decide whether microservices scale your org or stall it. Draw them by data ownership and team, not by code size. The rules.
Guide · 6-part series
Microservice Service Design: Boundaries That Hold
A connected series on getting microservice boundaries right: service ownership, bounded contexts, and the data-and-team rules that decide whether your services scale your org or stall it.
-
- Microservices
Bounded Contexts in Real Microservice Systems
Bounded contexts are how you find real microservice boundaries: split where the same word means different things. The practical guide, not the DDD theory.
- Microservices
Breaking Service Dependency Cycles
Service dependency cycles make microservices impossible to deploy, test, or reason about in isolation. How to detect them and four ways to break them.
- Microservices
Shared Libraries in Microservices: The Real Cost
Shared libraries in microservices promise reuse but quietly recouple services through a versioned dependency. When they help, when they hurt, and the rules.
- Engineering Strategy
Platform Service Design for Internal Teams
Platform service design means building internal services as products for your own engineers. The golden-path model, the self-service rule, and what to avoid.
- Microservices
Modular Monolith vs Microservices: How to Choose
Modular monolith vs microservices: start with a modular monolith and extract services only when a real force demands it. The decision framework and the signals.
Newsletter
Follow the series
New posts in this series and others, when there is something worth saying. No spam.