Serverless vs. Traditional Hosting   Hosting a web application involves choosing the right... Tagged with hosting, webdev, javascript, beginners.

Roberto Umbelino

Figma

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Compare serverless hosting and traditional hosting for web applications by evaluating their costs, benefits, and drawbacks. Serverless hosting, with its auto-scaling and pay-per-use model, is ideal for applications with unpredictable traffic. In contrast, traditional hosting offers fixed pricing and full control, making it suitable for consistently high traffic applications. Examples of providers include AWS Lambda for serverless and DigitalOcean for traditional hosting.

Serverless vs. Traditional Hosting

Examples of Traditional Hosting Providers:

Is free tier enough for you?
Yes -&gt; Serverless,
No -&gt; VPS,
What is a VPS? -&gt; Managed Hosting

I don’t understand why serverless don’t provide straight forward option to temporarily shutdown service/account based on cost limit set by user.

Even AWS Elastic Bean Stalk is a serverless hosting

But , I think the serverless more expensive if I have a lot of requests, or high load , am I right?

From my own experience I’d still don’t understand quite much why choose serverless option, which is much expensive when traditional hosting is dirt cheap and it covers 90% of the use cases. Not everybody is building huge services with huge flows and resource hogging.