3 ms·
How did this came to be known as serverless? It just seems to be an extreme case of microservices running on someone else's computer?
by kabes 10y ago
How did this came to be known as serverless?
It just seems to be an extreme case of microservices running on someone else's computer?
- dingaling 10y ago> How did this came to be known as serverless? Indeed, 'blameless' would seem more appropriate. All the best trying to recover a 'serverless' application when one portion fails; lots of late-night phone-calls and picking-through the terms of SLA documents in that future compunded by the fact that most serverless advocates say that you can dispense with operations staff...
- easytiger 10y agoThe other buzzwords have run out.
- Skinney 10y agoI think it might have something to do with the fact that the payment model isn't connected to a server instance, but how often your code is run. Heroku, GAE etc. are server-oriented. Your code is running on a dyno or an instance, and you pay based on the number of instance-hours you use. In AWS Lambda, or Azure Functions, you pay for the number of requests you process and the time spent processing those requests, how many instances are spent processing those requests are irrelevant. It's a serverless payment modell.