I can appreciate the appeal of a Backend-as-a-Service offering like Firebase, particularly if you're a one-person frontend-heavy dev team; it seems like it gives you a lot of leverage in the early experimentation stages. I'd like to play with it some day soon.
But this sort of incident really underscores the business value of having an exit strategy from whatever cloud you're running in.
That's why I like Kubernetes, since you can just spin up a new cluster on whatever cloud you want (or on-prem), and all your app deploy scripts remain the same.
Likewise for the choice of boring data store (Postgres/MySQL). I'm happy to pay a cloud provider to run my DB for me, because I know I can trivially redeploy in another hosted DBaaS or on-prem solution if I had a need to do so.
You could make the same case for running your stack on VMs that you manage; pick your poison.
But this sort of incident really underscores the business value of having an exit strategy from whatever cloud you're running in.
That's why I like Kubernetes, since you can just spin up a new cluster on whatever cloud you want (or on-prem), and all your app deploy scripts remain the same.
Likewise for the choice of boring data store (Postgres/MySQL). I'm happy to pay a cloud provider to run my DB for me, because I know I can trivially redeploy in another hosted DBaaS or on-prem solution if I had a need to do so.
You could make the same case for running your stack on VMs that you manage; pick your poison.