Overview and Application Scenarios

Application Scenarios

DDM provides the following methods of configuring shards to meet different service needs.

Method 1: Keep shards unchanged and increase data nodes

This method does not change the number of shards and only increases data nodes. Some shards are migrated from original data nodes to new data nodes, but shard data is not redistributed. So this method is the fastest one among all three methods and is recommended.

This method underpins rapid service growth after horizontal sharding and can reduce costs at the early stage of services. It is also suitable if RDS for MySQL instances cannot meet storage space and read/write performance requirements.

Figure 1 Adding RDS for MySQL instances with shards unchanged

Method 2: Add shards with data nodes unchanged

This method adds shards, but not data nodes. It changes total shards, total table shards, and table sharding rules. Data is redistributed to all shards. Old tables in original shards will be deleted, and broadcast tables are increased.

This method is suitable if associated RDS for MySQL instances have sufficient storage space but one of its tables contains a large amount of data, with query performance limited.

Figure 2 Adding shards with RDS for MySQL instances unchanged

Method 3: Add both shards and data nodes

This method increases both shards and data nodes. It changes total shards, total table shards, and table sharding rules. Data is redistributed to all shards. Old tables in original shards will be deleted, and broadcast tables are increased.

This method is suitable if associated RDS for MySQL instances cannot meet storage space and read/write requirements and there is a physical table containing a large amount of data with query performance limited.

Figure 3 Adding shards and RDS for MySQL instances