3 ms·
Like "cloud computing", the name "serverless" doesn't make much sense when used literally. It doesn't mean that there are no servers involved, just that there a
by CharlesW 9y ago
Like "cloud computing", the name "serverless" doesn't make much sense when used literally. It doesn't mean that there are no servers involved, just that there are none to be directly managed by the developer.
P2P also doesn't mean "no servers", but that every node is as much server as client.
Amazon popularized but didn't invent the term "serverless", which appears to have been first used in 2012.[1]
[1] http://readwrite.com/2012/10/15/why-the-future-of-software-and-apps-is-serverless/ http://readwrite.com/2012/10/15/why-the-future-of-software-a...
- losteric 9y agoFunctions-as-a-service seems clearer to me
- CharlesW 9y agoMe too! It also works nicely when thinking about the IaaS ⟷ PaaS ⟷ FaaS continuum of abstraction.
- dannyw 9y agoEventually we'll get to LaaS, where instead of having to find, test, and integrate libraries, you type in some natural language like "send an email", and pop down a guaranteed-compatible-for-X-years, 100% uptime, edge-case-handled function that automatically bills per execution directly to your FaaS account, no registration or invoicing required.
- _hyn3 9y ago> It doesn't mean that there are no servers involved, just that there are none to be directly managed by the developer. They already had stuff like that. S3. RDS. Elasticache. At least the cloud gives you the nebulous feeling of servers off in the ether somewhere. But serverless is neither specific nor accurate. It doesn't work. It's nothing more than lazy marketing-speak.
- closeparen 9y agoThe name for "just give us your code and we'll run it" has been PaaS for a while.