So I'm no fan of whiny prescriptivism language complainers, but "serverless" really takes the cake for a pointlessly confusing neologism.
-
-
Not saying serverless is a perfect term, and I would welcome a better one. But I think the snark about it is tiresome.
-
I'm mostly trying to figure out what is different about it vs Heroku (there are things!) and the name obscures more than it helps.
-
FaaS is better, I think.
End of conversation
New conversation -
-
-
The servers are still a bit more front-and-center in Heroku's model. You don't administer them yourself, but you know about & pay for them.
-
"Dyno" is a server in your mind?
-
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 -
-
-
“Heroku helps you run your server process – with Lambda you don’t run a server process at all, just functions”
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.