High-performance service-side access design

Yesterday read a post, the overall summary of the next service optimization of several points, but also for these days to read the book to make an annotation

Original link: http://www.liuhaihua.cn/archives/424955.html

1 Read and write separation, access from the library, write operation access to the main library, the main library will synchronize the change data to from the library.
2 Resolve write delay, increase MySQL cache, use high-performance CPU host, MySQL use physical host, use SSD
3 Vertical Sub-Library, the irrelevant business stripping, reduce the use of join. Implement the business in the program rather than in SQL.
4 a horizontal sub-library that splits large traffic into multiple parallel units, leveraging the Unified ID generator with cache redis.

The idea is to make the best possible squeeze performance from the physical architecture, the hardware level, to provide a higher level of access at a single point
3,4 's idea is to move the operation logic of the database into the program, the database is usually very difficult to leave, especially the level of the library, need to have a set of data access logic for the late integration of data.

High-performance service-side access design