Theoretically, the data from the slave database is not synchronized to the main database, and changes to the data structure of the slave database do not affect the data in the main database. This can be done.
But there are potential problems:
The slave database has a unique index on a certain field, but the master database does not have such a setting. Synchronization data may fail to be inserted, causing synchronization interruption
The slave library directly modified the structure, and the data of the main library could not be stored in the database at all, and the synchronization failed
When the primary machine fails, the data structure of the backup machine is inconsistent, which affects recovery and business replacement
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Theoretically, the data from the slave database is not synchronized to the main database, and changes to the data structure of the slave database do not affect the data in the main database. This can be done.
But there are potential problems:
The slave database has a unique index on a certain field, but the master database does not have such a setting. Synchronization data may fail to be inserted, causing synchronization interruption
The slave library directly modified the structure, and the data of the main library could not be stored in the database at all, and the synchronization failed
When the primary machine fails, the data structure of the backup machine is inconsistent, which affects recovery and business replacement
SO, it’s up to you