If an RDS instance is overloaded, you can vertically split a database or table from this instance into a separate instance. This topic describes how to use the dual-write solution and simple splitting solution to achieve vertical splitting.
Background information
Assume that Database A and Database B are deployed on an RDS instance. The instance is facing bottlenecks because of business growth. If you want to reduce the load on the instance, you can vertically split Database B into a separate instance. For more information, see, Dual-write solution and Simple splitting solution.
Precautions
- You must create a separate instance as the destination instance. The database account
of the destination instance must have the same permissions as the database account
of the source instance. For more information about the supported destination instance
types, see Overview of data migration scenarios.
Note We recommend that you create and authorize a database account for the source and destination instances. This allows you to distinguish session information and improve data security.
- You must add the connection string of the destination instance to the application.
- If you use the Simple splitting solution, you must pause your business and stop writing data to the database for a short period of time. To minimize the impact on your business when you change and release a program or switch instances, we recommend that you split the database during off-peak hours.