Bahahahahahaha! What a riot!
> More replicas will help with READ scenarios
One Master and many Slaves helps scale READs.
> but how can we enhance WRITE scenarios with multiple masters?
No, you can't. Period. End of discussion. Here's why: All writes must be performed on all replicas.
So it's freakin' useless for multimaster.
"Hello, I'm interested in sharding our data using mysql fabric. From everything I've read thus far mysql fabric requires that clients hit the shard key when making requests/queries. Is it possible to just use a vanilla SQL client like mysqlworkbench or sequel pro to query our sharded database without hinting?"
"It depends a little on what you want to do. There is no problems using a normal connector to connect to one of the servers in the sharded system, but the trick is figuring out which one. This is the functionality that a Fabric-aware connectors provides."
Rest in piss, libmysqlclient. You will not be missed.
Burn in Oracle, hell.
(Tip, go check out rethinkdb.com!)