> Perhaps the name it should be called is adminless or backend as a service What's odd is that we already have "infrastructure as a service", which is generall

> Perhaps the name it should be called is adminless or backend as a service What's odd is that we already have "infrastructure as a service", which is generally what this is. An entire infrastructure to run your code, without having to set it up (although you still need to configure logging to get useful data in most situations, it seems).