Service decomposition strategies in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is service decomposition in microservices?

Service decomposition is the process of breaking down a large application into smaller, independent services that each handle a specific business capability.

beginner

Name one common strategy for decomposing services based on business capabilities.

Decomposing services by business capabilities means creating services that align with distinct business functions, like 'Order Management' or 'User Profile'.

intermediate

What does the 'Decompose by Subdomain' strategy mean?

It means splitting services according to different subdomains identified in the business domain, often using Domain-Driven Design concepts to isolate bounded contexts.

intermediate

Why is it important to avoid tight coupling between decomposed services?

Avoiding tight coupling ensures services can be developed, deployed, and scaled independently, improving flexibility and fault isolation.

advanced

What is a drawback of decomposing services too granularly?

Too fine-grained services can lead to increased complexity in communication, higher latency, and more operational overhead.

Which of the following is NOT a common service decomposition strategy?

A Decompose by user interface layout

B Decompose by database schema

C Decompose by subdomain

D Decompose by business capability

Decomposing by user interface layout is not a recommended strategy because UI concerns should not dictate service boundaries.

What is the main goal of service decomposition?

A To split an application into independent services with clear responsibilities

B To create a single monolithic application

C To increase database joins

D To reduce the number of services

Service decomposition aims to create independent services that focus on specific business functions.

Which design approach helps identify subdomains for decomposition?

A Test-Driven Development

B Waterfall Model

C Domain-Driven Design

D Continuous Integration

Domain-Driven Design helps identify bounded contexts and subdomains for service boundaries.

What is a risk of having tightly coupled microservices?

A Easier independent deployment

B Better scalability

C Improved fault isolation

D Harder to change one service without affecting others

Tight coupling makes it difficult to change or deploy services independently.

Which factor should NOT primarily influence service boundaries?

A Team organization

B UI design

C Database technology

D Business capabilities

UI design should not dictate service boundaries; services should focus on business logic.

Explain the main strategies used to decompose a monolithic application into microservices.

Think about how to split responsibilities clearly and keep services independent.

Describe the advantages and disadvantages of decomposing services too finely.

Consider what happens when services become very small.