Serverless: A lesson learned the hard way

Re:Serverless: A lesson learned the hard way by le-mark on Thursday August 10, 2017 @02:09PM (#14982452)

Off topic, but the "serverless" moniker needs to die. I propose "adminless" as in "server I don't have to admin, configure, or patch" as being much more descriptive of whats really going on.

[ Parent | on HN ]

Re:Serverless: A lesson learned the hard way by nathancahill on Thursday August 10, 2017 @02:22PM (#14982594)

Eh, if I'm deploying a cloud function, the server truly doesn't exist for me. It's more like a Web Worker running in a privileged environment. I'm ok with the name.

[ Parent | on HN ]

Re:Serverless: A lesson learned the hard way by sidlls on Thursday August 10, 2017 @03:22PM (#14983166)

No, it's really a server running your function. You just (are told you) don't have to worry about the server or what it's actually doing.

[ Parent | on HN ]

Re:Serverless: A lesson learned the hard way by dvfjsdhgfv on Thursday August 10, 2017 @03:29PM (#14983233)

> You just (are told you) don't have to worry about the server

...until you receive the $206 bill for the work done by the server.

[ Parent | on HN ]

Re:Serverless: A lesson learned the hard way by nathancahill on Thursday August 10, 2017 @03:31PM (#14983249)

But that works on the VPS level too. We're just talking about higher levels of abstraction on top of hardware. Which one stops being a "server"? I'd argue that once you lose the OS, it's no longer a "server".

[ Parent | on HN ]

Re:Serverless: A lesson learned the hard way by motoboi on Thursday August 10, 2017 @02:21PM (#14982575)

Well, it's not adminless either, as AWS have lots of them keeping the hosts alive and running.

But if you can ignore that, you can probably also ignore the fact that your code runs on a server.

[ Parent | on HN ]