Distributed design - Copy
Others
2019-08-25 10:22:39
views: null
effect
- For data backup, high availability
- Improved throughput, high-performance
classification
- Master-slave architecture
- performance
- A master from multiple, separate read and write, to improve throughput
- Availability
- Main library a single point, once hung, can not be written
- Availability from the library
- consistency
- Data synchronization there is a delay, when read back from the library may be old data
- solution
- Simply ignored, there is a delay is normal
- For real-time required by interface, read directly from the primary database
- In the case of separate read and write, to snatch a problem occur concurrently resources
- Interface consistency requirement, not separate read and write, only the operation of the master library
- Multi-master architecture (back up each other)
- performance
- Availability
- consistency
- And a master-slave architecture as
- Master-slave from master
- high performance
- High Availability
- consistency
- Standby
- Main library provides literacy services, prepared by the library to do with failover
- General performance
- Set the cache to improve performance
- High Availability
- No consistency
- Ali cloud and widespread use 58
Principle mysql master-slave synchronization
Origin www.cnblogs.com/oklizz/p/11406952.html