Microservices Architecture
Service decomposition, API gateways, and communication patterns
Microservices Architecture
Microservices decompose an application into small, independently deployable services, each running its own process and communicating via lightweight protocols (HTTP/gRPC/events).
Microservices Architecture
Communication Patterns
- Synchronous (REST/gRPC): Direct request-response. Simple but creates coupling. Use for queries that need immediate response.
- Asynchronous (Events/Messages): Publish-subscribe via message queue. Decoupled but eventual consistency. Use for commands that can be processed later.
- API Gateway: Single entry point for all services. Handles routing, auth, rate limiting, SSL termination.
- Service Mesh: Infrastructure layer (Istio, Linkerd) handling service-to-service communication, observability, and security.
- Saga Pattern: Manage distributed transactions across services using a sequence of local transactions with compensating actions.
Monolith vs Microservices
text
āāāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāā¬āāāāāāāāāāāāāāāāāāāāāāā
ā Aspect ā Monolith ā Microservices ā
āāāāāāāāāāāāāāāāāāāāāāā¼āāāāāāāāāāāāāāāāāāāāāā¼āāāāāāāāāāāāāāāāāāāāāāā¤
ā Deployment ā Single unit ā Independent services ā
ā Scaling ā Scale entire app ā Scale per service ā
ā Development ā Simple initially ā Complex from start ā
ā Team Size ā Small teams ā Large organizations ā
ā Data Consistency ā ACID transactions ā Eventual consistency ā
ā Latency ā In-process calls ā Network calls ā
ā Debugging ā Single process ā Distributed tracing ā
ā Technology ā Single stack ā Polyglot ā
ā When to Use ā MVP, small teams ā Scale, large teams ā
āāāāāāāāāāāāāāāāāāāāāāā“āāāāāāāāāāāāāāāāāāāāāā“āāāāāāāāāāāāāāāāāāāāāāā