It's a straw man to assume that "serverless" refers to physical servers. The argument is triggering my irony detector, since that usage is itself a marketing c

It's a straw man to assume that "serverless" refers to physical servers. The argument is triggering my irony detector, since that usage is itself a marketing category so broad as to be meaningless. Only in the client-server model does "server" have a definition worth reasoning about, where "server" refers to the passive listening endpoint in that model. Lambda's published reference architecture is asynchronous invocation via queues listening to pub/sub events, which in integration terms is the antithesis of the client-server model. There is no listening server in the client-server sense. So whilst the term "serverless" has obviously been chosen as a catchy marketing term for the mouthful that is "asynchronous event-driven self-scaling platform-as-a-service", it's not wrong.