> What you're saying is you're managing my servers for me cool! Servers as a service or something like that But that’s what virtual machines or container host

> What you're saying is you're managing my servers for me cool! Servers as a service or something like that But that’s what virtual machines or container hosting services are doing. This is a level of abstraction higher than that - there’s no link between you code and any server instance. Ultimately when your code runs, it runs on a piece of hardware - a server. But it’s up to the serverless provider to choose where. If during the day your function call is invoked a million times, it could be run on the one or a million servers anywhere in the world. I think serverless is a better term for that than ultra or easy servers, when you don’t have to think about provisioning the size or quantity of servers you require. A better real world analogy might be the kitchens that share a seating area in a mall. Although they might still be considered ‘restaurants’ the are also ‘restaurantless’ as the tables and seats are provided to them/their customers on an as needed basis. A kitchen can serve as many diners as they are able, table provisioning is handled by someone else.