High cohesion in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does high cohesion mean in microservices?

High cohesion means that a microservice focuses on a single, well-defined task or responsibility, making it easier to understand, maintain, and scale.

beginner

Why is high cohesion important in microservices?

High cohesion helps reduce complexity, improves code quality, and allows teams to work independently on different services without causing conflicts.

intermediate

How does high cohesion relate to service boundaries in microservices?

High cohesion guides defining clear service boundaries so each microservice handles related functions, avoiding mixing unrelated features in one service.

intermediate

Give an example of low cohesion in a microservice.

A microservice that handles user authentication, order processing, and payment all together has low cohesion because it mixes unrelated responsibilities.

intermediate

How does high cohesion improve scalability in microservices?

Because each microservice handles a focused task, it can be scaled independently based on its specific load, making the system more efficient.

What is a key characteristic of a highly cohesive microservice?

A It handles many unrelated tasks.

B It focuses on a single responsibility.

C It depends on many other services.

D It has a large codebase.

High cohesion means focusing on a single responsibility to keep the service clear and manageable.

Which of the following is a benefit of high cohesion in microservices?

A Easier to scale independently.

B Harder to maintain.

C More dependencies.

D Increased complexity.

High cohesion allows each service to be scaled independently based on its workload.

What problem can low cohesion cause in microservices?

A Better team autonomy.

B Simplified deployment.

C Clear service boundaries.

D Mixing unrelated features in one service.

Low cohesion mixes unrelated features, making services complex and harder to maintain.

How does high cohesion affect team collaboration?

A Teams can work independently on different services.

B Teams must coordinate on every change.

C Teams share the same codebase for all features.

D Teams cannot own services.

High cohesion allows teams to own focused services and work independently.

Which practice supports achieving high cohesion in microservices?

A Combining multiple unrelated features in one service.

B Sharing databases between services.

C Defining clear service boundaries based on business capabilities.

D Avoiding service decomposition.

Clear service boundaries based on business capabilities help maintain high cohesion.

Explain what high cohesion means in microservices and why it matters.

Think about how a focused service is easier to manage.

Describe how high cohesion influences the design of service boundaries in a microservices architecture.

Consider how to split a system into smaller parts.