Serverless is one of the most transformative paradigms in cloud computing. AWS Lambda, API Gateway, DynamoDB, and the broader serverless ecosystem let you build and scale applications without ever thinking about servers. It’s fast to develop, often cheap to run, and incredibly powerful.
But here’s the thing: serverless is not a silver bullet.
After years of building on AWS, I’ve seen teams adopt serverless for everything — and sometimes pay the price in performance, cost, complexity, or all three. The best architects don’t just know when to use a tool. They know when not to.
In this article, I’ll walk you through five real-world use cases where going serverless is the wrong choice, and what you should consider instead.
1. Long-Running, Compute-Heavy Workloads
The Problem
AWS Lambda has a hard timeout of 15 minutes. If your workload takes longer than that, Lambda simply isn’t an option. But ev…
