Read "Large Web site Technology architecture: Core Principles and Case studies" chapter I: Evolution of large-scale website architecture

Write in front

　　From the beginning to write code to now, has done several projects, BS and CS have, has always been a code of farming. However, as a progressive programmer, there is an ideal to become an architect. So, in peacetime work, but also actively to see a variety of books, see the Garden inside the fine article. Hope, in this pursuit of the dream of the road, can leave little bit, also is a kind of consolidation of knowledge, some share.

Reading experience

Soon after work, I read the first chapter of the book. There is some understanding of the architecture evolution of the website.

(1) Structure of the initial website: a server, application, database, files are all on one server. Lmap is sufficient.

(2) The architecture of Level two website: Application Service and Data service separation, the concurrent processing ability and data storage space of the website are greatly improved.

(3) The structure of level three Web site: Add cache, including server local cache and distributed cache, the data access pressure has been greatly improved.

(4) The architecture of level four Web site: Using the application server cluster, the load Balancer Dispatch server, you can distribute access requests to people in the server cluster and one, to address the load pressure of the site.

(5) Level five Web site architecture: Database Read and write separation, application server when writing data, access to the main database, the main database through the master-slave replication mechanism to update data synchronization to the slave server, when the application server read data, directly to the database to obtain data. In order to facilitate application access to read-write separated databases, the application server side usually uses a dedicated data access module, so that data read and write separation to the application transparent.

(6) The structure of level six Web site: Using reverse proxy and CDN to accelerate the response of the website, in order to return data to the user as early as possible, speed up user access, while reducing the pressure of the backend server.

(7) The structure of level seven Web site: Using Distributed File system and distributed database system, the most common is the business sub-Library, the different business databases deployed on different physical servers.

(8) The architecture of level eight Web sites: using NoSQL and search engines to provide better support for scalable distributed features, the application server accesses a variety of data through a unified data access module, alleviating the hassle of application management of many data sources.

(9) Level nine Web site architecture: Business splitting, splitting a site into many different applications, and deploying and maintaining each application independently. Applications can be linked through a hyperlink, or distributed through Message Queuing, most of which constitutes an associated complete system by accessing the same data storage system.

(10) The architecture of Level 10 Web site: Distributed services, each application system needs to perform many of the same business operations, can be extracted from these shared services, independent deployment, through the distributed service calls shared business services to complete the specific business operations.

As a matter of this, the evolution of the large Web site architecture is almost. Although the company's project is still at the second level, from the book, I learned that the evolution of the site, and the technical means involved in it, is a lot of benefits.

Read "Large Web site Technology architecture: Core Principles and Case studies" chapter I: Evolution of large-scale website architecture