PolarDB-X 1.0 scales by partitioning data across multiple ApsaraDB RDS for MySQL instances. Partitioning distributes both read/write traffic and storage, so neither concurrency nor capacity becomes a single bottleneck.
How partitioning works
PolarDB-X 1.0 uses two complementary partitioning strategies:
| Strategy | Description |
|---|---|
| Horizontal partitioning (database sharding and table sharding) | Distributes rows across multiple ApsaraDB RDS for MySQL instances based on computing or routing rules. PolarDB-X 1.0 provides multiple algorithms to match different data distribution scenarios. |
| Vertical partitioning | — |
Together, these strategies let read/write requests run in parallel across instances while spreading storage load across the cluster.
Horizontal partitioning
Horizontal partitioning uses computing or routing rules to determine which ApsaraDB RDS for MySQL instance stores each row. PolarDB-X 1.0 includes multiple algorithms to handle different sharding requirements.
The following diagram illustrates how PolarDB-X 1.0 distributes data across ApsaraDB RDS for MySQL instances using horizontal partitioning:
