Summary of TaurusDB Best Practices

This document describes some detailed common practices to help you easily use TaurusDB.

**Table 1** TaurusDB best practices
Category	Reference	Description
Data migration	From ECS-hosted MySQL to TaurusDB	Describes how to migrate data from self-managed MySQL databases to TaurusDB.
Data migration	From Other Cloud MySQL to TaurusDB	Describes how to migrate data from MySQL databases on other clouds to TaurusDB.
Read/Write splitting	User Authentication	Describes how to grant remote login permissions to an account.
	Connection Pool Configuration	Describes how to configure a connection health check mechanism.
	Routing Read Requests to the Primary Node	Describes how read requests are routed to the primary instance.
Backup and restoration	Restoring Data of a Deleted Instance	Describes how to restore deleted instance data on the console.
	Restoring Data of Deleted Databases	Describes how to restore deleted database data on the console.
	Restoring Data of Deleted Tables	Describes how to restore deleted table data on the console.
Cold and hot data separation	Partition-Level Cold and Hot Data Separation	Describes how to implement cold and hot data separation for partitioned tables.
Cold and hot data separation	Database-Level Cold and Hot Data Separation	Describes how to implement database-level cold and hot data separation.
Security	Security Best Practices	Provides guidance on TaurusDB security configurations.
Monitoring alarms	Suggestions on TaurusDB Metric Alarm Configuration	Describes how to configure TaurusDB metric alarm rules.

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

For any further questions, feel free to contact us through the chatbot.