Cloud Computing
Microservices in the Cloud
Amazon's "Bezos API Mandate" in 2002 required all teams to expose services via APIs with no direct database access between services. This mandate created AWS - Amazon discovered it had built a cloud platform while decomposing its retail monolith. The microservices pattern is not an organizational trend; it is the architecture behind the most reliable large-scale systems in the world.
- Netflix runs ~700 independently deployed microservices. A bug in the recommendations service does not affect video playback.
- Uber decomposes rider-driver matching into geolocation, ETA estimation, surge pricing, dispatch, and payment services - each scaled independently.
- Lyft built Envoy proxy internally to handle inter-service communication; it became a CNCF project used by Airbnb, Apple, and Google.
Service Discovery
**Service Discovery** is a foundational pattern in Microservices in the Cloud. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Service Discovery is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Service Discovery?
API Gateway
**API Gateway** is a foundational pattern in Microservices in the Cloud. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
API Gateway is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of API Gateway?
Circuit Breaker
**Circuit Breaker** is a foundational pattern in Microservices in the Cloud. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Circuit Breaker is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
What is the primary operational benefit of Circuit Breaker?
Service Mesh
**Service Mesh** is a foundational pattern in Microservices in the Cloud. It addresses specific operational, scalability, or cost challenges that cloud-native architectures face at scale.
Service Mesh is a standard topic in AWS Solutions Architect and senior cloud engineering interviews. Understanding the trade-offs and failure modes is more valuable than memorizing the exact API.
Microservices in the Cloud is primarily a theoretical concern - real teams just use managed services and ignore architectural patterns
Managed services reduce operational burden but do not eliminate the need for sound architectural decisions about failure modes, scaling, and cost
Managed services handle undifferentiated heavy lifting (patching, backups, failover) but the choice between them, their configuration, and their integration patterns still require deep architectural understanding.
What is the primary operational benefit of Service Mesh?
Key Ideas
- **Service discovery:** services find each other at runtime via DNS (Cloud Map) or registry (Consul) rather than hard-coded endpoints
- **API Gateway:** managed entry point handling auth, rate limiting, routing, and TLS termination before requests reach backend services
- **Circuit breaker:** stops sending requests to a failing service and returns a fallback until recovery - prevents cascade failures
- **Service mesh:** Istio/Linkerd handles mTLS, retries, load balancing, and observability without application code changes
Related Topics
These topics form the broader Microservices in the Cloud ecosystem:
- Event-Driven Architecture — Async messaging decouples microservices - queue failures do not block service-to-service calls
- Performance Tuning — Connection pooling and caching are especially critical in microservices due to amplified network call counts
- Multi-Cloud and Hybrid — Service mesh provides a consistent communication layer across cloud and on-premises microservices
Вопросы для размышления
- How does the architecture for Microservices in the Cloud change when scaling from 1,000 to 10 million users?
- What are the primary failure modes in a Microservices in the Cloud system, and what monitoring detects them before users are affected?
- What trade-offs would change the architectural decision for Microservices in the Cloud in a regulated industry with strict data residency requirements?