Hacker News Reader

Isn't that what webhosting providers have offered for at least a decade? No server management, just resources on a server with a web server, data storage (often MySQL) and the ability to execute code (mostly PHP). You run your software on a server without ever accessing the server itself or having to worry about OS updates.

View on HN

I think the biggest difference is webhosting provider can't scale your php resource up and down infinitely in real time. Your software is not exposed to the server but constrained by it. The idea of serverless is that your service is automatically distributed and not constrained by the capability of some web server.

Infinitely?

To scale shipping static content, I'd rather look into CDN with proper caching, instead of maintaining ten layers of abstraction just to feel good about how modern my stack is.

Yes, but what about non-static?

Also, a CDN would also classify as "serverless", under the definition used by the article.

Reply on news.ycombinator.com