This chapter covers
- Scoping microservices based on business capabilities and use cases
- When to scope microservices to reflect technical capabilities
- Making design choices when service boundaries are unclear
- Scoping effectively when multiple teams own microservices
Designing a new feature in a microservice application requires careful and well-reasoned scoping of microservices. You need to decide when to build new services or extend existing services, where boundaries lie between those services, and how those services should collaborate.
Well-designed services have three key characteristics: they’re responsible for a single capability, independently deployable, and replaceable. If your microservices have the wrong ...