4 ms·

Check out the book "High Performance MySQL" at http://shop.oreilly.com/product/0636920022343.do http://shop.oreilly.com/product/0636920022343.do from chapter 9

• petilon 12y ago
  Replication works for managing read load, but it doesn't help manage write load. This is when you need automatic sharding. As far as ACID, many applications don't need it, for example in a game application users will forgive you if you lose their latest scores, but in a banking application users will not forgive you if you lose their last deposit. So it depends on the application.
  • cthalupa 12y ago
    >Replication works for managing read load, but it doesn't help manage write load. This is when you need automatic sharding. You've said 'need automatic sharding' multiple times now, but you've still yet to explain why you need it. Yes, sharding is important for write scaling. But it doesn't "need" to be automatic. Plenty of setups have completely capable manually sharded workloads running on MySQL. Some would consider the manual approach a plus, vs. relying on the database to automagically do it. It can be nice to have automatic sharding, assuming it works properly. But nice and needed are two different things, an I think it's an important distinction. You're basically saying if you shard you have to go with mongo and you can't go with anything that requires you manually handle it.