What is Serverless?
#31 · Level 2 · Scaling and resilience · ServerlessConcept
Section titled “Concept”Serverless means there are servers, but you don’t have to think about them at all. Setting up servers, updating them, working out how many you need — AWS handles all of it. When the load rises or falls, the service grows or shrinks on its own. You usually pay only for what you use. On AWS, Lambda, API Gateway, Fargate, S3 and DynamoDB are well-known examples of serverless services, which you can combine to build a complete app.
Simple example
Section titled “Simple example”If you own a car, fuel, servicing and parking are all your job. If you take an Uber, you just say where you’re going, and pay only for the ride. Serverless is the Uber of the cloud.
Why it’s needed
Section titled “Why it’s needed”For small tasks (such as shrinking an image when it’s uploaded), there’s no need to keep a server running all day. The work runs when it arrives and stops when it’s done, and you pay only for that time.
Where it’s used
Section titled “Where it’s used”API backends, processing files, tasks that run at set times, and event-driven tasks. On AWS, Lambda, API Gateway, DynamoDB, SQS and Fargate are serverless services.
Azure equivalent
Section titled “Azure equivalent”Azure Functions, Logic Apps, Container Apps
Related
Section titled “Related”AWS Lambda · Amazon API Gateway · AWS Fargate
Learn more
Section titled “Learn more”For details and the latest information, see the official documentation: