पाठ 1 / 32
What Serverless Really Means
यह पाठ अभी हिंदी में अनुवादित नहीं है, इसलिए अंग्रेज़ी में दिखाया जा रहा है।
Define serverless precisely, separate it from "no servers", and name the properties and trade-offs of the model.
लेखक: Rahul Agarwal · 15 साल से वेब डेवलपर
Servers still exist; you just stop managing them
Serverless does not mean there are no servers. It means you do not provision, patch or scale them: the cloud provider does. Two ideas usually travel together. Functions as a Service (FaaS), such as AWS Lambda, Azure Functions or Google Cloud Run functions, run a small piece of your code in response to an event. Managed backend services (object storage, queues, managed databases, authentication) replace servers you would otherwise run yourself. Three properties define the model. You are billed for actual use rather than for idle capacity. Capacity scales automatically with traffic, often all the way down to zero when nobody is using the app. And the unit of deployment is small: a function, not a machine image. The trade-off is control. You accept limits on execution time, memory and the runtime environment, and you design around the fact that an instance may be created or destroyed at any moment.
Owning a car versus booking a cab
Owning a car is like running a VM: you pay the EMI and insurance even while it sits parked. Booking a cab is serverless: you pay per ride, someone else services the vehicle, and during the Diwali rush more cabs appear. But you cannot modify the cab, and sometimes you wait a little for one to arrive. That wait is the cold start you will meet later.
Interview trap: serverless is not only FaaS
Many students answer "serverless = Lambda". The better answer: serverless is an operational model. A database billed per request (for example DynamoDB on-demand mode), object storage, or a container platform that scales to zero (for example Google Cloud Run) are also called serverless, because you do not manage or pay for idle servers.
त्वरित जाँच: Which statement best describes serverless computing?
- Code runs without any physical servers being involved
- The provider manages servers and scaling, and you pay mainly for actual use
- All application code runs inside the user's browser
- It is a hosting option that only works for static websites
Answer
The provider manages servers and scaling, and you pay mainly for actual use — Servers still exist, but provisioning, patching and scaling are the provider's job, and billing follows usage. Browser-only code and static hosting are different things.