Website architecture theory
Pure theory is a complete recombination of other people's things.
I. reference materials
Http://insights.thoughtworkers.org/website-architecture-evlovement/, this is the main reference.
Http://blog.csdn.net/moonpure/article/details/44671773
Http://baike.baidu.com/link?url=NNU1TR8S_MEmoXQvmZNq05mlYWgvK-e7b1vzN_yRAQgBV11O537tP5ijShyVYGSPnsJNgXn8DlcY5N8GrZAGEpa2BbaUcpK6AHdlN0wS_FbJjqFS2YUwO6WYRp7PiJAA
Http://www.cnblogs.com/Leo_wl/p/4281236.html
II.
Http://jingyan.baidu.com/article/456c463b95e6030a583144b6.html Baidu experience
Http://www.cnblogs.com/junneyang/p/5231849.html
Http://www.cnblogs.com/xrq730/p/4954152.html
Http://www.thinkphp.cn/code/2510.html
Two episodes of http://blog.csdn.net/dinglang_2009/article/details/46398885
= =
Website architecture is a gradual process.
1. Stand-alone era. APP, DB, File are all on the same server.
2. The application server is separated from the database server.
3. Application server cluster. Increase the number of application servers and how to interact with multiple application servers
4. Database read-write separation. It leads to two problems: 1, master-slave synchronization; 2, the application's choice of database.
5. Use search diligence to relieve the pressure of reading the library (InnoDB)
6. Use cache to relieve the pressure of reading database (redis as database cache, memcacahe as application cache)
7. Split database horizontally and vertically
8. Split the application, refine the business, and then split out multiple application servers
9. Introduce message middleware
Technical improvements brought about by the increase in business
1. Separation of application server and database
2. Add page cache (CDN)
3. Add page fragment cache
4. Data caching (database information)
5. Add application servers ()
6. Database sub-database
7. Sub-tables, DAL and distributed caching
8. Add more application servers
9. Read-write separation (database), cheap storage equipment
10. Large distributed applications and low-cost server clusters
