Microservices
読み方：Microservices
An architectural approach where an application is built as a collection of small, independently deployable services, each responsible for a specific business function. Services communicate via APIs. Contrasts with monolithic architecture. Used by Netflix, Amazon, and Uber at scale.
What are Microservices
Microservices architecture decomposes a large application into small, focused services (user service, order service, payment service) that each run independently and communicate via APIs. Each service can be deployed, scaled, and updated without affecting others.
Microservices vs. Monolith
| Aspect | Monolith | Microservices |
|--------|----------|---------------|
| Deployment | All at once | Per-service |
| Scaling | Scale everything | Scale bottlenecks only |
| Team structure | One codebase | Independent teams |
| Complexity | Lower | Higher |
| Fault isolation | Single point of failure | Failure contained to service |
When to Use Microservices
Microservices add operational complexity. They're appropriate when:
- • Multiple teams are working independently on different product areas
- • Different services have dramatically different scaling needs
- • You've already hit the limits of a monolith
The Right Starting Point
Start with a monolith. Extract services when specific pain points appear. Netflix didn't start as microservices—they migrated from a monolith as scale demands required it.