If I were on GCP and had paying customers, I would use Cloud Spanner. It's expensive, but it's a good piece of technology.
The key is to choose your entity wiseley. I wrote an app inside Google that did on the order of 10,000 writes per second and it was no problem; each entity group only showed up once every minute or so.
However, it has been my personal experience that Cassandra handles instances going down much better than it handles instances getting very slow but staying online. In that case Cassandra will work extra hard to just spin its wheels. If you know that is what is happening you can be better off manually bringing those nodes offline.
My sympathies lie with Discord users. I’m sure it’s ruining a lot more weekend plans with them.
I’ve both a discord user and someone that has spent years in an on-call rotation that included nights and weekends.
If you tell your customers that you have an outage because AWS is down, they will shrug and say, things happen. You are in the same boat with a lot of other people, you will no more get blamed for AWS being down than if the whole city lost power. No one ever got fired for choosing AWS.
If you’re on Azure, you might get a funny look from people who only know about AWS, but since it is Microsoft Azure you will get a pass.
But people will judge you for choosing GCP. Any little thing that goes wrong, they will be questioning why you didn’t choose AWS.
https://status.discordapp.com/