Serverless refers to you administering the application and its resources but not the server directly. Yes, at some level servers are involved, but generally the organization deploying applications is not responsible for administering the hardware, the OS, other resources, often including the scaling of the server resources: they're only concerned with the administration of the application. One can argue that at some level the organization deploying the application is often still concerned with the underlying server and where that line is drawn, but many find it meaningful to make such a distinction.
Re:Serverless Best Practices
by a_silly_name on Monday September 03, 2018 @01:51PM
(#17903937)
Does make sense, but your description (and others) seems to match most vendors API out there today. It's not clear to me what 'serverless' means vs 'hosted / managed infrastructure', or even 'external API'.
It doesn't seem like a technical term at all.
Another commenter mentioned that it applies only to the price list, and that makes sense to me.
The pricing model is the only thing that seems to be serverless as far as I can tell.
Re:Serverless Best Practices
by a_silly_name on Monday September 03, 2018 @01:52PM
(#17903941)
I'm going with this for now, thank you!
Serverless... pricing models. The pricing models are just silent.
I'm mystified by the word 'serverless'. Why are we using this word? There are clearly, _quite clearly_ servers involved. The wacky bugs involved in these 'server-less' services... are going to come down to what's happening on the servers involved.
EDIT: my question seems to have offended. Unfortunate, and unintentional!