Using DB business split to solve the problem of high writing pressure
With mysql copy and read and write separation to solve the problem of reading pressure, then write pressure can also be copied to solve?
The answer is no:
Use cache merge to write multiple times into one time, for example: the number of views can be written into redis, and then write mysql once it reaches n.
Splitting databases into unused server clusters:
Reasonably design libraries and tables to avoid splitting operations after cross-database queries:
Create new db clusters on demand
Synchronously split db into new clusters
Migrate database accounts to corresponding new clusters
Modify an app's data connection
delete chain
