When to use microservices (and when not to) - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a microservice in simple terms?

A microservice is a small, independent part of a big software system that does one job well and can work on its own.

beginner

When is it a good idea to use microservices?

Use microservices when your system is big, needs to grow fast, different teams work on different parts, or you want to update parts without stopping the whole system.

beginner

What are some reasons NOT to use microservices?

Avoid microservices if your system is small, simple, or your team is small because it adds extra work and complexity.

intermediate

How do microservices help with scaling?

Microservices let you grow only the parts that need more power, like adding more cooks only to the busy kitchen station instead of the whole restaurant.

intermediate

What challenges come with microservices?

They need good communication between parts, careful planning, and tools to watch and fix problems because many small parts can be tricky to manage.

Which situation is best suited for microservices?

A A large app with many teams working on different features

B A simple calculator app

C A small website with one developer

D A static brochure website

Microservices work well when many teams build different parts of a large app.

What is a common downside of using microservices?

A Simplifies deployment

B Increases system complexity

C Reduces communication needs

D Eliminates need for monitoring

Microservices add complexity because many small parts must work together.

When should you avoid microservices?

A When the team is small and system is simple

B When the system is very large

C When you want to scale parts independently

D When you have multiple teams

Small teams and simple systems do better with simpler designs.

How do microservices improve system updates?

A By requiring all parts to update together

B By updating the whole system at once

C By avoiding updates

D By updating one part without stopping others

Microservices let you update one part without affecting the rest.

What is a key requirement for microservices to work well?

A No communication between parts

B One big database for all parts

C Strong communication and monitoring tools

D No need for planning

Good communication and monitoring are essential for managing many small services.

Explain when microservices are a good choice and when they are not.

Think about system size, team size, and complexity.

Describe the main challenges of using microservices and how they affect system design.

Consider what managing many small parts involves.