-
Hello seth_e,
Thanks for sharing your thoughts on this item.
You’re absolutely right that in real-world scenarios, both Lambda and Fargate could be valid depending on traffic patterns. If the workload is continuous and high-volume, Fargate may indeed be more cost-effective, while Lambda shines when traffic is bursty or unpredictable with idle periods.
To clarify, unpredictable workloads refer to traffic patterns that fluctuate without a consistent baseline, such as sudden spikes, seasonal surges, or irregular request volumes that are difficult to forecast. In these cases, provisioning fixed compute capacity can lead to either over-provisioning (wasted cost) or under-provisioning (availability risks). Lambda’s event-driven scaling model is designed to handle exactly this kind of variability, automatically adjusting capacity without upfront planning.
Additionally, the scenario explicitly emphasizes requirements such as being stateless, REST-compliant, highly available, scalable for unpredictable workloads, and cost-efficient. These keywords strongly align with Amazon API Gateway and AWS Lambda, which is why that option is considered the best fit in this case.
I hope this helps! Let us know if you need further assistance.
Regards,
JR @ Tutorials Dojo
