In recent years, many new serverless service providers have been released for everything (Neon – Postgres, Cloudflare D1 – SQLite-like DB, GCP Functions, Vercel edge functions, etc.). However, people have been complaining about their complexity and overkill in the beginning.
More recently, I've witnessed friends prefer serverful providers for their apps because they offer more control, and are cheaper and simpler to get started with (their words). Serverful platforms like Render, Railway, or Fly.io have also become a bit more popular.
Both approaches come with their trade offs and limitations, especially at different scale and costs.
So, which way, western man: is Serverful the Future? Quo vadis, web development?
As tech progresses, it makes the abstraction levels better for those who need less power.
Nothing has shifted. It might have gained some market share but that's about it.
There are times though when serverless may not be a good idea:
- Atypical technology stack. If the stack you need, and actually need, isn't accounted for then you're on your own.
- Continuous, 24x7 application load. You'll have to do the cost analysis, but you may find you're better off provisioning a server.
- You want to "lift and shift" existing assets into the cloud.
Brand-new, greenfield project? Consider serverless first.
I'd also say things like Neon "serverless postgres" is not really serverless. It is using serverless as the de jour marketing term for managed postgres SaaS. I can get the same thing from GCP (Cloud SQL) for much less
Serverless or serverful any will get the job done.
But for personal projects, I like its charge-by-usage model. I want my projects be cashflow positive.