Serverless is usually used to describe things like AWS Lambda, or Azure functions. You write your code, and push it to the cloud, and don't really think about t

Serverless is usually used to describe things like AWS Lambda, or Azure functions. You write your code, and push it to the cloud, and don't really think about the infrastructure. It is "serverless" in that you don't need to think about individual servers. You just deploy your code, and only pay for the time it actually spends executing. I've also seen serverless used to describe services like Google App Engine and the Azure App Service. They're a bit less granular than cloud functions, since you deploy entire applications instead of individual functions. Again, you don't really have to think about servers or infrastructure. You deploy your code, and it just runs and scales up as necessary. Docker and k8s and containers are great in general, but require a lot more hands-on active management than the services I usually see described as serverless. Though even here, services like AWS Fargate and Azure Kubernetes Service and (I think) Google Container Engine take a lot of the manual work out of container orchestration.