Sharding - Oracle to Aurora MySQL Migration Playbook
Oracle UsageMySQL Usage
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Sharding

Feature compatibility Amazon SCT / Amazon DMS automation level Amazon SCT action code index Key differences

No compatibility

No automation

N/A

MySQL doesn’t support sharding.

Oracle Usage

Sharding is a method of data architecture where table data is horizontally partitioned across independent databases. These databases are called shards. All of the shards make up a single logical database, which is referred to as a sharded database (SDB). Sharding a table is process of splitting this table between different shards where each shards will have sharded table with the same structure but different subset of rows.

Oracle 18c introduces following sharding enhancements:

  • User-defined sharding. Before Oracle 18c data was redirected across shards by system. With user-defined sharding, users are now able to explicitly redirect sharded table data to specific individual shards.

  • Using JSON, BLOB, CLOB and spatial objects functionality in a sharded environment. You can now use these objects in sharded tables.

For more information, see Overview of Oracle Sharding in the Oracle documentation.

MySQL Usage

There is no equivalent option in MySQL. The most equivalent option will be to create application level sharding management that will interact with data that is spread across multiple instances.

Another option will be to assess the requirements and probably use another data store such as Amazon Redshift, Amazon EMR, or Amazon DynamoDB.