If you are able to be cost effective and run services on firebase, then keep doing so. Please! If you need to do something that doesn’t map well to firebase, t

If you are able to be cost effective and run services on firebase, then keep doing so. Please! If you need to do something that doesn’t map well to firebase, then my next stop would be AppEngine. If what you want to run won’t map well to AppEngine, then start looking at K8S. For me, this is usually wanting to run some kind of legacy system, or where a higher level of security is needed, or if you want or need to plan to run across multiple cloud vendors or in a mixed workload environment. If AppEngine has been covered by google’s BAA when I started my current gig, I would have just used that, with k8s to handle the couple of oddball things that we are using that wouldn’t run as well there. Personally, it’s not about scale so much as certain kinds of architectures or problems. You might have a system that needs to run a smallish number of nodes, but has reasons for needing what kubernetes offers without wanting to reinvent the wheel yet again with the existing cast of characters.