Practice vocabulary for describing service decomposition: bounded context, extracting services from monoliths, granularity trade-offs, and decomposition strategies.
0 / 5 completed
1 / 5
A developer says: 'We should ___ the monolith by business capability.' Which word fits?
'Decompose by business capability' means splitting a system into services aligned with distinct business functions like payments, orders, or users.
2 / 5
'We ___ the payment service from the monolith last quarter.' Which verb is correct?
'Extracted' is the standard verb: you extract a service from a monolith when you carve it out into a standalone deployable unit.
3 / 5
A tech lead says: 'This service is too ___-grained — it only handles one database row.' What word is missing?
'Too fine-grained' means the service is too small and granular, adding overhead without clear business value. The opposite, 'coarse-grained', means too large.
4 / 5
'We ___ these two services to reduce overhead.' Which word completes this sentence?
'Merged' describes combining two services back into one, often done when the operational overhead of keeping them separate outweighs the benefits.
5 / 5
What is a 'bounded context' in microservices vocabulary?
A 'bounded context' (from Domain-Driven Design) defines the boundary within which a particular domain model is valid and consistent — foundational to service decomposition.