[jethro_tell]

serverless is when you save the state but don't keep a machine sitting around when there are no requests, so you'd keep your calendar state in a hosted db and when someone asks for the calendar, a thread spins up and creates the calendar from the state and then disappears until there is another request. This is basically the exact opposite of serverless

[rustyminnow]

> serverless is when you [...] don't keep a machine sitting around when there are no requests

FTFY

The key part of serverless is that you don't have a server idling around. Whether or not you use a hosted db is not relevant.

[outworlder]

And you may even use some 'serverless' DB services. Or not. The app is still serverless.

[drexlspivey]

This can easily run on Cloudflare workers, you don't even need a server

[jcelerier]

... what do you think those are

[adamrezich]

this thread is making me feel like I'm going crazy

[aliqot]

Mmm yes, this one reminds me of the microservices debacle from a few years ago about when does your monolith technically become a microservice. I can't find the link, but I think we were unable to clearly define at which point your monolith has become a true 'SoA' group of microservices.

[vlovich123]

The generous interpretation of what op said is that you don’t have to maintain a server in any way or shape which is indeed the case. You only write business logic while the infrastructure automatically connects it to handle inbound requests.