Cost saving is one of the top reasons people choose cloud computing. In this example of a simple API system, over a few generations of its evolving architecture, we excel at serverless.

This illustration shows a typical journey from hosting an application in a data center, then moving it to the cloud with elastic compute, then modernizing it to containerization, and eventually rewriting or converting it to serverless. A technology stack migration like this.

On-Premises	VM, F5, Java, RDMS (database)	$$$
Lift and Shift	EC2, ELB, Java, EC2 (database)	$$$
Cloud native	EC2, ELB, Java, RDS, Auto Scaling	$$
Container	ECS/Fargate, ELB/API Gateway, Java, RDS	$
Serverless	Lambda, API Gateway, Python, Aurora Serverless	$

Serverless is not a panacea to all your compute challenges. Please validate your use case and make your best fit selection. If you are dealing with a new application, consider going from the bottom up. That means serverless first!