SQLite was already serverless.

https://www.sqlite.org/serverless.html

> SQLite was already serverless.

Yes but now it runs on someone else server! Wait a minute, this makes no sense...

'serverless' is perhaps the stupidest marketing buzzword developers have come up with.

Indeed it's quite stupid. Any alternative catchy name for the concept?

We already had terms that covers about 90% of the different use cases: “managed”, “SaaS”, “shared hosting”, “multi-tendency”, “timesharing”.

tendency > tenancy (or tenant)

Yeah sorry, that must have been autocorrected on my phone. The words are visually similar enough that it’s easy to miss.

Dunno about the catchy, but Runtime as a Service could fit the *aaS pattern.

I thought the term was FaaS?

Homeless - of no fixed abode.

Catchy like vagrant but perhaps a bit insensitive (unless it was used to highlight the plight of the homeless).

Less catchy - Poste Restante or General Delivery

https://en.m.wikipedia.org/wiki/Poste_restante

"Shared hosting".

I would agree and here's why: when compared to PHP scripts of old, the concept is the same. You have some bit of executable code that gets called when a specific URL is hit.

Shared hosting is better than this. You get to use the filesystem.

sysadmin-less, or "someone else server"

Isn't the modern serverless just a "load on demand"-concept?

My intuition is:

"Don't care where it runs, don't want to manage it, I want to pay only for when I actually use it, thanks for managing it, here's some extra cash for the effort"

(Neo-)Serverless just means billing per-request instead of per-day, right?

More or less yes.

But you can only apply that metric if you remove the end users from actually touching the machines (virtual or real).

This is the "less" in serverless.

Turns out that this is also something people want: not having to be on the hook for actually administering machines, installing security patches etc etc.

So managed (platform as a) service + fine grained billing

I would have preferred something like daemonless, processless, or something that more closely describes what's being offered. My suggestions also are flawed but less flawed than serverless, imho.

How about "inetd"?

Managed infrastructure

Managed service

NoSrv

Cloudy

Cloudy McCloudface

computer-free software

well, you don't need to manage a server to run the process. So, technically, it is less server. It's not no-server, just less.

According to your link:

> Recently, folks have begun to use the word "serverless" to mean something subtly different from its intended meaning in this document. Here are two possible definitions of "serverless": Classic Serverless: [...] Neo-Serverless: [...]

SQLite was already "Classic Serverless". Now it's "Neo Serverless" as well.