So I'm no fan of whiny prescriptivism language complainers, but "serverless" really takes the cake for a pointlessly confusing neologism.
-
-
More so than a lambda. Virtualized, yeah, but still. Maybe my mental model is wrong; I think of it as a server in an elastic scaling group.
-
it's a pre-requisite resource you're responsible for spinning up before deploying code. Lambda doesn't have this. Your resource *is* code
-
You have to "deploy" a lambda and it feels not that different to me. But other details (size, framework in the platform) matter.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.