> The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway. So yes, there is a server indeed. Why call it "serverless" then ?

> The wrapper to fit Lambda into a client-server synchronous-invocation world is API Gateway. So yes, there is a server indeed. Why call it "serverless" then ? because one part of the stack uses pubsub ? then call that part a worker queue because that's what it is.