7 ms·
Some people prefer to call it Function as a Service, which in most cases is closer to what it actually is. "serverless" does not refer to the absolute lack of
by iagooar 10y ago
Some people prefer to call it Function as a Service, which in most cases is closer to what it actually is.
"serverless" does not refer to the absolute lack of servers - it refers to the fact that your CODE (applications and software in general) should not be AWARE of being executed on a physical or virtual machine.
The platform should be as abstract as it gets. I always imagine it as coding on a piece of paper: in a way, my code should work and make "sense", even though we all know that a piece of paper won't execute any instructions. And this is part of the magic of "serverless" software: it imagines a perfect, abstract machine where it can run, forgetting about the complex, unreliable, physical machine underneath.
It's an almost philosophical approach to writing software and getting it needs some time and thought. And needless to say, it does not solve ALL your problems, but it MIGHT solve SOME of your problems.
- stephenr 10y ago> it refers to the fact that your CODE (applications and software in general) should not be AWARE of being executed on a physical or virtual machine. With the exception of para-virtualised device drivers, what code is ever aware of being executed on physical or virtual machines?
- windowsworkstoo 10y agoC'mon now, you know what was meant...
- stephenr 10y agoNo, I honestly don't, using that definition. AWS Lambda and similar services have literally nothing to do with hardware vs software. They're about running a function in response to an event on someone else's stack, almost like the `map` part of a `map-reduce`, if the input was considered to be distinct events/objects.
- beambot 10y agoOr just RPC writ large.
- hueving 10y agoI don't think it has to do with the way the application is written at all. It's how it's deployed and managed.