Firstly because you don't provision servers to run the code, the runtime will scale the infrastructure horizontally with response to traffic. Secondly because i

Firstly because you don't provision servers to run the code, the runtime will scale the infrastructure horizontally with response to traffic. Secondly because it's not a client/server architecture from the perspective of the code being run. Basically it's "serverless" because you the developer are not doing anything with servers. You're not writing one, maintaining one, or managing the infrastructure to run one. You drop off a blob of logic to the cloud provider and they handle everything else for you, and you pay on demand. Functions-as-a-Service (FaaS) is another name for the same idea but less catchy