DRDS has the following features:
DRDS supports database/table sharding of RDS for MySQL instances. After creating a distributed database, select a shard key, based on which DRDS then generates sharding rules to implement horizontal sharding.
You can configure read/write splitting by using RDS read-only instances or standby MySQL instances to help your application handle transactions, read-only instance failure, standby instance failure, and specified active/standby access. You can configure read/write splitting on the DRDS console.
If the data storage capacity or traffic reaches the bottleneck, DRDS supports online storage capacity expansion without modifying the application. You can visually track the progress of the capacity expansion.
You can elastically expand service capabilities by changing the number of resources.
DRDS comes with proprietary O&M instruction sets such as SHOW SLOW, TRACE, and SHOW NODE for distributed databases to help you identify and locate issues quickly.
DRDS supports distributed and globally unique sequences. With this feature, you can meet service requirements for primary or unique keys and specific scenarios when using distributed databases.
DRDS supports the single-host-like MySQL account and permission system to guarantee the security of operations performed by different roles.
DRDS works with the distributed transaction kit GTS to support distributed transactions and guarantees data consistency of distributed databases.
DRDS supports real-time monitoring and alerts for core resource indicators and database instance indicators, such as instance CPUs, network I/O, and active threads, so that you can promptly identify resource and performance bottlenecks.