In a previous post, I wrote an overview about Spider for MySQL with its advantages and disadvantages. Now I’ll go through a simple example demonstrating how to implement Spider for MySQL.

System information:

MySQL instances information (shards):

• Server: 3 VMs (here in after will be mentioned as mysqla “192.168.56.51”, mysqlb “192.168.56.52” and mysqlc “192.168.56.53”).
• OS: CentOS 6.4
• RAM: 512MB
• MySQL version: 5.5.43 (tar-balls)
• Download link: http://dev.mysql.com/get/Downloads/MySQL-5.5/mysql-5.5.43-linux2.6-x86_64.tar.gz

Continue reading →

Having big tables is one of the expected database problems, especially, for the fast growing database systems. In fact, big tables itself is not a problem but with big tables, the following problems are strongly expected:

1. Retrieving data from big tables is so slow.
2. It is a very hard job to maintain those tables like adding/removing an index, adding/dropping/modifying a column, … etc.
3. System resources, especially, the IO system might not be able to handle such huge traffic of writes and reads.
4. When it comes to the reporting queries, it might be a horrible nightmare!
5. Always cause disk space problem.

Continue reading →