One of the biggest arguments (among many others) for going serverless is the dramatic cost reduction you experience. Since the whole gist of serverless is that you only pay for the time your code is executed, it will result in significantly lower AWS bill (in most cases). Sounds too good to be true? Let’s see what some early adopters of serverless have said about it:
90% cost reduction on a small non-mission critical application
Avner Sorek has shared how he moved a simple Express.JS application (a side project with 50-150 daily visits) — from AWS Elastic Beanstalk to Lambda+APIG. The whole migration took less than a day and it resulted in a ~90% reduction of costs - from $44.95 to $6.12 per month. See the graph below:
Anver’s website is called libhive and it’s built in Node.JS with ExpressJS, and backed by DynamoDB.
AI application reduced monthly AWS bill from $30 000 to $4000
Mohsiur Rahman from Heavywater writes how their previous infrastructure kept getting more and more expensive for them: “Even with most of our EC2 instances sized as t2.micro, our AWS bills kept increasing. In the span of just 4 months, our monthly bill increased from $10K to $30K with over 1,000 EC2 instances running.”
Just by going serverless, their infrastructure costs went down to $4000 from close to $30 000 at one point. See the graph below:
Heavywater Inc is using artificial intelligence virtual assistants to offer business process outsourcing.
Serving 39 million requests for $370/month (instead of $10 000)
Adam Pash writes how he solved a $10 000 per month hosting bill problem at Postlight by going serverless (running on AWS Lambda and API Gateway, built and deployed using the Serverless framework).
They used AWS Lambda for everything - “from parsing the web to writing Slack bots; from batch resizing hundreds of thousands of photos in parallel to batch transcoding hundreds of thousands of videos.”
Serverless technology is still fairly new and an uncharted territory for the majority of technology companies, but all the early adopters that have embraced it, are very happy with their choice.
These 3 case studies above are clear indicators how switching to serverless can save you a ton of money. At the same time, serverless isn’t a “one-size-fits-all” and the experiences with cost reduction might vary based on the application type. If you have your story to share, just let us know in the comments below!
NB: if you want to optimize your costs and application performance even further, make sure you check out Dashbird!