It's not a lie, and it's not misleading. The concept of 'server' loses all meaning in this given architecture. You create 'Lambdas' - units of functionality -

It's not a lie, and it's not misleading. The concept of 'server' loses all meaning in this given architecture. You create 'Lambdas' - units of functionality - and they do that they are supposed to do entirely independent of the underlying architecture. In fact, using the concept of 'server' in a Lambda situation probably obfuscates the situation and adds unnecessary complexity. A 'server' is an implementation detail that concerns only those providing the container/Lambda services. As long as the implementation lives up to the SLA (i.e. performance, uptime, security, price, redundancy) that you have agreed to - then it doesn't matter how it works.