My biggest problem with the "serverless" term is that it's a solution to a few different problems conflated into one term. * Not having to manage a server. *

My biggest problem with the "serverless" term is that it's a solution to a few different problems conflated into one term. * Not having to manage a server. * Not having to have dedicated resources which can be wasteful. * Having an architecture that scales. When most people talk about serverless, they mean something that solves all three of those problems. When I think of serverless, I think it only needs to solve the first problem. What if I don't want to manage a server, but I want dedicated resources? I just want to deploy a standard web app (written with node js for example) with a postgres backend and preallocated resources but without having to maintain a server? Is that serverless?