If you want an excuse to try a Serverless approach with AWS Lamdba here it is.
In July, we served 9 million + API calls through API Gateway to AWS Lambda.
And the cost last month for AWS Lambda?
Yes, that’s 64 cents.
9 million isn’t that many if you break it down into a per second count (FYI 31 days ~ 2.6 million seconds so it’s around 3.36 API calls/second on average) but it’s non-trivial in scaling terms.
And we do quite a lot with that, including storing, processing, providing data to users, basically lots of business logic… We don’t have an API that doesn’t do much.
Our biggest costs for the month?
Backing up our data into S3, then offsite, cost us quite a lot more (we use DynamoDB which should mean backing up is far less of an issue, but I’m from the paranoid school of thinking that says “back it all up anyway”). In fact, that cost us more than I’d like but I’m certain it can be significantly reduced because we haven’t optimised this cost yet (and to be honest, it’s not actually worth anybody’s time to do that yet).
Also, we pay for support from AWS of course.
But in comparison to the cost of actually delivering our API and products…
Beat that all you container enthusiasts and you EC2 afficionados with your maintenance and upgrade requirements and libraries to support.