this is a fair critique of what I would call "first-gen" serverless platforms, like AWS Lambda. it's a shame that it's ~5ish years late to the party.

because "just use a container" is more or less the solution that "second-gen" serverless platforms all offer.

but also this:

> A container keeps state (just add a Docker volume!)

is just absolutely terrible as general-purpose advice.

like, yes, it can be annoying that "serverless" platforms are generally stateless, which forces you to move your state into a hosted database of some kind.

but...that reflects the underlying reality of the cloud platform. the servers that your "serverless" code runs on are generally themselves stateless.

if you were to blindly follow this "just add a Docker volume" approach to managing state, you're in for a rude awakening the moment you want to scale your "serverless" code from 1 server to 2 servers.

and unsurprisingly, the article glosses over this a few paragraphs farther down:

> You can deploy one container, or ten. Scale them. Monitor them. Keep state. Run background jobs. Use your own database.

run 10 containers...each with their own Docker volume? use my own database? what. this is blogspam nonsense.