Skip to main content

MySQL Sharding using ProxySQL | MariaDB Maxscale | MySQL ScaleArc | MySQL Router | MySQL Fabric

Sharding:

Sharding means scale out. Each node runs MySQL instance. Data is partitioned across all nodes. Sharding key is used to distribute data across nodes.
 
Example of sharding:

  • Each customer store data in their own schema
  • MySQL instance per customer
  • OS instance / container per customer
  • Environment per customer includes database server
  • Application server and required components

Ref:

MariaDB MaxScale - https://mariadb.com/products/technology/maxscale
ScaleArc - http://www.scalearc.com/how-it-works/performance-features/query-routing
MySQL Fabric -
https://www.percona.com/blog/2014/04/25/managing-farms-of-mysql-servers-with-mysql-fabric/
https://downloads.mysql.com/docs/fabric-1.5-en.pdf

Explore Sharding and commonly used solution for MySQL sharding:

https://severalnines.com/blog/database-sharding-how-does-it-work
 
 

 
Labels:

Comments

  1. William L. HoneySeptember 26, 2024 at 10:51 PM

    This comment has been removed by the author.

    ReplyDelete
  2. Richard FetzerJuly 26, 2025 at 3:58 AM

    Sharding is a smart way to scale MySQL by splitting data across multiple servers, each handling its own chunk to boost performance and reliability. Honestly, WebSpaceKit makes managing sharded databases feel seamless and efficient, especially when scaling apps for fast-growing businesses.

    ReplyDelete

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more