Use cases
Case studies

Why Serverless?

Just like wireless internet has wires somewhere, serverless architectures still have servers somewhere.

What ‘serverless’ really means is that as a developer you don’t have to think about those servers. You just focus on code.

What makes an application serverless?

4 key properties of Serverless Applications you should know about

Zero administration

Deploy code without provisioning anything beforehand, or managing anything afterward. There is no concept of a fleet, an instance, or even an operating system. No more bothering the Ops department.


Let your service providers manage the scaling challenges. No need to fire alerts or write scripts to scale up and down. Handle quick bursts of traffic and weekend lulls the same way -- with peace of mind.


Function-as-a-service compute and managed services charged based on usage rather than pre-provisioned capacity. You can have complete resource utilization without paying a cent for idle time. The results? 90% cost-savings over a cloud VM, and the satisfaction of knowing that you never pay for resources you don't use.

Increased velocity

Shorten the loop between having an idea and deploying to production. Because there's less to provision up front and less to manage after deployment, smaller teams can ship more features. It's easier than ever to make your idea live.

Next Steps

Check out all the different use cases for serverless applications. Take a peek at how the Serverless Framework compares to other software. Talk to us directly on the enterprise contact form

Or if you’re ready, follow our step-by-step guide to start building a Serverless Application with your favorite language.