Microservices characteristics - System Design Guide

Problem Statement

Monolithic applications become hard to maintain and scale as they grow. Changes in one part can affect the entire system, causing slow deployments and frequent outages.

Solution

Microservices break down a large application into small, independent services. Each service handles a specific business function and can be developed, deployed, and scaled independently.

Architecture

Service A

→Service B

↓

Database A

This diagram shows independent microservices communicating with each other and each having its own database, illustrating service isolation and autonomy.

Trade-offs

✓ Pros

→

Each service can be developed and deployed independently, speeding up releases.

→

Failures in one service do not directly affect others, improving system resilience.

→

Services can be scaled individually based on demand, optimizing resource use.

→

Teams can own specific services, improving focus and expertise.

✗ Cons

→

Increased complexity in managing multiple services and their communication.

→

Requires robust monitoring and logging to trace issues across services.

→

Data consistency is harder to maintain due to distributed databases.

When the application is large and complex, requiring frequent updates and independent scaling of components. Typically beneficial when teams are large and can own separate services.

For small applications with simple functionality and low traffic, where the overhead of managing multiple services outweighs benefits.

Real World Examples

Netflix

Solved the problem of scaling video streaming by splitting functionality into microservices like user management, recommendations, and playback control.

Amazon

Used microservices to allow independent teams to develop and deploy services like product catalog, order processing, and payment handling.

Uber

Handled complex ride matching, payments, and notifications by breaking the system into microservices for better scalability and fault isolation.

Alternatives

Monolithic Architecture

All functionality is built into a single deployable unit without service boundaries.

Use when: When the application is small, simple, and requires minimal scaling or independent deployments.

Modular Monolith

Application is divided into modules within a single process, without separate deployment units.

Use when: When you want clear code separation but want to avoid the operational complexity of microservices.

Summary

Microservices split applications into small, independent services focused on specific business functions.

They enable independent development, deployment, and scaling, improving agility and resilience.

However, they introduce complexity in communication, data management, and operations.