Cloud, containers, serverless, edge, and deployment architecture
Deployment architecture maps logical workloads and data to physical failure domains, trust zones, regions, capacity pools, and lifecycle mechanisms. Cloud services change responsibility; they do not remove it.
Core ideas and patterns
| Idea | What it solves | Cost, limit, or warning |
|---|---|---|
| IaaS/PaaS/SaaS | Trade control for managed responsibility at different layers | Shared-responsibility boundaries must be explicit |
| Containers/orchestration | Package processes and automate placement/lifecycle | Kubernetes adds a distributed control plane |
| Serverless/FaaS | Scales event-triggered functions with managed runtime | Cold start, limits, state, and provider coupling apply |
| Edge computing | Moves work near users/devices | Fleet, consistency, security, and disconnected operation grow |
| Sidecar | Adds a colocated supporting capability | Resource and lifecycle coupling are hidden |
| Ambassador | Proxies outbound connectivity for an application | Proxy failure and configuration affect the workload |
| Gateway aggregation | Reduces client round trips | Gateway can become a latency and ownership hotspot |
| Deployment stamp/cell | Replicates an isolated scale unit | Fleet automation and placement are required |
| Multi-region active-active | Serves and writes from multiple regions | Conflict, cost, and operational complexity are high |
How to apply it
Draw production deployment nodes, zones, regions, network paths, identity boundaries, data replication, autoscaling inputs, quotas, secrets, and control-plane dependencies. Calculate capacity and recovery at each failure domain. Define immutable delivery, progressive rollout, and rollback.
Evidence, not opinion
Test zone/region loss, quota exhaustion, image/supply-chain policy, cold starts, rescheduling, secret rotation, backup restore, DNS failure, and control-plane degradation. Measure cost per transaction.
Small example
A stamp serves 2,000 tenants with its own application pool, cache, queue partition, and database shard. Routing metadata assigns tenants; new stamps add capacity and contain noisy-neighbor impact.
Feynman check
Explain the design to a new engineer without using the pattern names. State the problem, the forces that conflict, the chosen boundary or mechanism, what can fail, and the evidence that would prove the choice still works.