Think of a container as a standardized shipping box for software. Instead of sending raw code, package the application, its runtime, and its dependencies into an image. The cloud provider manages the hardware and host operating system; containers launched from the image are identical clones. section 9.4.2
That package can travel from a laptop to an AWS server with the same environment, helping avoid “it works on my machine” surprises. CaaS is a middle ground: less operating-system overhead than managing a virtual machine, while preserving control over the application environment. section 9.4.2
Before choosing CaaS, weigh the operational tradeoffs:
- Portability: package only what the application needs, then deploy the same image across environments. section 9.4.2
- Orchestration: a fleet of containers needs a system such as Kubernetes to place them on servers and restart them after crashes. section 9.4.2
- Running cost: billing continues while containers are awake and running. section 9.4.2
Table 9.1 Architect’s Cheat Sheet: The Compute Spectrum
|
Model
|
What It Is
|
Control Level
|
"Clarity" Best Use Case
|
The Hidden Architectural Trap
|
|
IaaS (Virtual Machines)
|
Renting the metal.
|
High (OS-level access)
|
Legacy applications or strict legal/compliance
requirements.
|
"Lift and Shift":
Moving legacy problems to the cloud and paying 24/7 for idle time.
|
|
CaaS (Containers)
|
Renting the shipping port.
|
Medium (Environment &
runtime)
|
Standardized, portable deployments across different
environments.
|
Orchestration Overhead: You
still have to manage the complex system (Kubernetes) and route the boxes.
|
|
PaaS (Platform as a Service)
|
Renting the runtime.
|
Medium-Low (App code &
config only)
|
Rapid prototyping and standard web apps, where you want
zero infrastructure chores without learning Docker.
|
The "Black Box": If
your app suddenly needs a custom system-level library, you are out of luck
and heavily locked into that vendor's ecosystem.
|
|
FaaS (Serverless)
|
Renting the millisecond.
|
Low (Pure logic/code)
|
Spiky traffic or new startups wanting infinite scale with
zero idle costs.
|
"Cold Starts" and Time Limits: Latency
spikes when waking up code, and hard execution limits that brutally kill
long-running processes mid-flight.
|
|
AIaaS (AI Models)
|
Renting the reasoning.
|
Zero (Prompts & payload)
|
Adding complex language or data processing without
building ML infrastructure.
|
Hallucinations: The model
confidently invents facts, requiring strict "RAG" guardrails.
|
Compare CaaS with other cloud compute models by control level, best use case, and architectural trap. section 9.4.6



