mwguy

I disagree.

“It’s not a genocide, they’re just killing more civilians than combatants

Every war in history kills more civilians than combatants. Normally that ratio is about 6:1.

starving out the population by blocking humanitarian aid,

Hamas is attacking aid trucks that are let in and stealing the aid to resell. It's not starving the population to stop aiding the people attacking you.

The amount of bullshit you spew on a regular basis is pretty impressive. Your comment history is like an Israeli propaganda primer. ... Sure.

Back at you.

There has been no verifiable evidence any hospital had any base anywhere near it.

Except the consisten video evidence, independent reports, and testimony dating back nearly a decade.

How else did you get music?

Was it the hospital that had a military base underneath it?

Which babies were proper prisoners of war?

You should be able to take the binlogs and upload them. Then in a restore situation you'd restore your last full db snapshot and replay your binlogs up until the point you lost the server.

If you truly need read/write to scale, multi-masrer clustering with MariaDB Galera is probably the best way to do it. They (MariaDB) also sell a load balancer/query proxy Max scale that can do a lot of surprisingly complex stuff (like publish new data to Kafka or centrally ship binlogs from one place to multiple read replicas).

However generally my advice is that if you're finding yourself trying to build a big relational database and writing to it a significant amount of times, it might be time to consider a different or at least modified architecture. Especially if your use case starts to scale to more than what Galera can handle. At some point, all these solutions become eventually consistent the more you scale. And if you are willing to accept eventual consistency, there are some clever ways to do storage using things like queueing, batching, caching etc that can scale horizontally much further than any relational database can.