Comments on: My first sharded MySQL application, 5 years later http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/ Stay curious! Thu, 02 May 2013 12:36:53 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Xaprb http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/#comment-20265 Xaprb Wed, 19 Sep 2012 20:25:53 +0000 http://www.xaprb.com/blog/?p=2867#comment-20265 We sharded because the data was too much for one server. In particular, the write load exceeded a single server’s capacity.

High Availability MySQL contains a lot of interesting advice. Maybe you can have a conversation with them about how well their suggestions worked in the real world on the large production applications they’ve built and maintained themselves.

]]> By: Daniël van Eeden http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/#comment-20264 Daniël van Eeden Wed, 19 Sep 2012 19:03:10 +0000 http://www.xaprb.com/blog/?p=2867#comment-20264 What about fan-in replication (aggregate the data of all the shards)? This is possible with a bit of scripting as explained in ‘High Availability MySQL’ or with Tungsten Replicator.

]]> By: Justin Swanhart http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/#comment-20263 Justin Swanhart Wed, 19 Sep 2012 18:33:28 +0000 http://www.xaprb.com/blog/?p=2867#comment-20263 Shard-Query has built in mapping capability. If you have a mapping of client_id to database you can extend the mapper to route queries to the right place if you put client_id=N into the where clause.

]]> By: Doron Levari http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/#comment-20261 Doron Levari Wed, 19 Sep 2012 18:13:25 +0000 http://www.xaprb.com/blog/?p=2867#comment-20261 Great post!

Disclaimer: I work for ScaleBase (http://www.scalebase.com/).
In ScaleBase, our goal is to make scale-out and sharding easy, complete and affordable. After all scale-out-using-data-distribution (AKA sharding) is the best way to scale!

With ScaleBase you’ll get some of you annoyances resolved:
1. ScaleBase is 1 address to the entire DB grid, MySQL compatible
2. cross-DB queries with aggregation, supporting GROUP BY, ORDER, LIMIT and more.
3. Unified picture for administration, and any tool MySQL, MySQLDump, MySQL Workbench, PHPMyAdmin…….
4. Redistribution of the data, add and remove DB nodes or withing current grid.
5. A bunch of more stuff.. take a look at our site

BTW – You did sharding back in 2007, you’re definitely one of the pioneers… Even on 2009, when I searched “sharding” in Google, it used to switch the word and say “did you mean sharing?”… today it’s 800K results…

]]> By: Xaprb http://www.xaprb.com/blog/2012/09/18/my-first-sharded-mysql-application-5-years-later/#comment-20256 Xaprb Tue, 18 Sep 2012 20:13:10 +0000 http://www.xaprb.com/blog/?p=2867#comment-20256 Sure, or shard-query. But the issue is more relevant for end-users than for IT department staff. If they are managing a number of clients on several shards, it is a pain for them to connect to the right ones, issue queries, and so on. There are commercial solutions for this, and I expect some of the vendors to post in the comments any second now ;-)

]]>