Serverless Vs Container Cost Tradeoff — AWS SysOps Administrator (SOA-C03)
Invocation Frequency Is the Cost Crossover Signal
When SOA-C03 asks you to choose between Lambda and container-based compute, the cost-deciding language is in the workload description. "Millions of short invocations" favors Lambda's per-request pricing. "Long-running processes" or "sustained high throughput" favors containers, where Lambda's per-duration pricing becomes expensive. "Spiky or unpredictable traffic" favors Lambda because idle containers still incur reservation costs. The phrase "cost-effective" paired with a workload profile is the exam's instruction to apply this tradeoff directly.
What This Pattern Tests
The exam presents a workload and asks you to choose between Lambda/API Gateway and ECS/Fargate or EKS. Lambda charges per invocation ($0.20/1M) plus duration ($0.0000166667/GB-second). Fargate charges per vCPU-hour ($0.04048) and GB-hour ($0.004445). At low, bursty traffic (< ~500K requests/day), Lambda wins because you pay nothing at idle. At steady high traffic (> ~1M requests/day), Fargate wins because the per-invocation overhead exceeds fixed compute cost. The crossover point depends on function duration and memory — the exam expects you to reason about it, not memorize a number.
Decision Axis
Traffic pattern determines compute model: bursty and unpredictable favors Lambda (zero idle cost), steady-state favors Fargate/ECS (lower per-request cost at volume).
Associated Traps
More Top Traps on This Exam
Decision Rules
When processing duration is well under 15 minutes, the workload is stateless, and the traffic profile is spiky with a near-zero baseline, Lambda with native SQS event-source mapping wins over Fargate on both operational overhead and cost because Fargate requires task-definition management and service auto scaling configuration that Lambda eliminates entirely.
Domain Coverage
Difficulty Breakdown