Serverless: slower and more expensive
I disagree with all the comments posted so far.<p>This should be a perfect use case for lambda, not &quot;oh you&#x27;re API is receiving more than 10M req&#x2F;day? Use Elastic Beanstalk instead with an EC2 instance and ELB&quot;. This kind of comment is just to abuse the free tier that AWS provide you with.<p>The whole idea of serverless is so you don&#x27;t have to manage infrastructure. OS patching, mucking around with Docker and and port fowarding rules are all removed once you go down the serverless route. Is it worth 8x the cost and 15% reduction in performance? The article argues no. If anything, AWS should price API GW and Serverless more competitively.<p>It&#x27;s nice to see though that the Firecracker implementation savings has been passed down to AWS Customers.<p>If the article saw a 1.5-2 times increase in cost, the debate would be much more interesting.<p>I&#x27;m in the container camp because serverless isn&#x27;t cheap and you can&#x27;t have long running processes.