> 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

> 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...