Serverless: 15% slower and 8x more expensive
-
I'm not trying to bash API Gateway, Lambda or serverless in general here, just showing that for some workloads they are a lot more expensive than boring old EC2 and Elastic Beanstalk.
Not gospel, but researched just enough for people to engage with whether it is wrong or right.
-
I'm not trying to bash API Gateway, Lambda or serverless in general here, just showing that for some workloads they are a lot more expensive than boring old EC2 and Elastic Beanstalk.
Not gospel, but researched just enough for people to engage with whether it is wrong or right.
Can't say I'm surprised that adding additional levels of abstraction comes with performance/pricing costs. The way the api gateway pricing clobbers applications that are chatty with lots of very small API calls instead of a handful of larger quasi-monolithic ones is really ugly though. I'd be somewhat curious what the relative pricing looks like for serving web pages since that's a much more common use (and would be a lot closer to relevant for me, needing to upgrade to .net core instead of adding new customer features would still be an issue). As it stands my AWS/net web app is only using lamba to trigger a few things on timers and thus orders of magnitudes of use below the limits for the free tier; everything else is running in VMs.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt