'Serverless' as currently jargoned is used to connote that the developer does not have to think about servers (or VM's or containers) directly. The 'serverless' buzzword does not mean that there are not servers somewhere doing useful work.
Sorry, can you elaborate in which way this is "does not have to think about servers"? Because almost the first thing on their tutorial is some messing around with AWS.
Serverless is really just an a community term for 'function as a service'. There are servers... you just upload discrete bits of code to the platform which executes them on demand.
Comments
'Serverless' as currently jargoned is used to connote that the developer does not have to think about servers (or VM's or containers) directly. The 'serverless' buzzword does not mean that there are not servers somewhere doing useful work.
Exactly, added a small piece of text to the README about this today: https://github.com/serverless/serverless/#why-serverless
Sorry, can you elaborate in which way this is "does not have to think about servers"? Because almost the first thing on their tutorial is some messing around with AWS.
Serverless is really just an a community term for 'function as a service'. There are servers... you just upload discrete bits of code to the platform which executes them on demand.