High Concurrency Website Solution

A small website, you can use the simplest HTML static page to achieve, with some pictures to achieve beautification, all the pages are stored in a directory, such a site for the system architecture, performance requirements are very simple. With the continuous enrichment of the Internet business, the site-related technology after these years of development, has been subdivided into very fine aspects, especially for large sites, the use of technology is very wide, from hardware to software, programming languages, databases, WebServer, firewalls and other fields have a high demand , is not the original simple HTML static site can be compared.

Large Web sites, such as portals, have a basic solution in the face of massive user access and high concurrent requests: the use of high-performance servers, high-performance databases, high-efficiency programming languages, and high-performance web containers. These solutions to some extent imply a greater investment.

2. HTML static

        In fact, we all know that the most efficient, The least expensive is the purely static HTML page, so we try to make the pages on our site with static pages to achieve, the simplest method is actually the most effective method. But for a lot of content and frequently updated sites, we can not all manually to achieve, so we have a common information distribution system CMS, like we often visit the various portals of the news channel, and even their other channels, are through the information distribution system to manage and implement, Information Publishing system can achieve the simplest information input automatically generated static pages, but also with channel management, rights management, automatic capture and other functions, for a large web site, has a set of efficient, manageable CMS is essential.

   In addition to portals and information publishing types of sites, for highly interactive community types of Web sites, as much as possible static is also a necessary means to improve performance, the community posts, articles in real-time static, updated time and then re-static is a lot of use of the strategy, A hodgepodge like mop is the use of such strategies, such as the NetEase community.

   At the same time, HTML static is also the means used by some caching policies, and for applications that frequently use database queries in a system but have little content updates, consider using HTML static to implement them. For example, forums in the Forum's public settings information, the current mainstream forum can be managed backstage and stored in the database, which is actually a large number of reception program calls, but the update frequency is very small, you can consider this part of the background update the time to static, so as to avoid a large number of database access requests.

4. Image Server Separation

   You know, for the Web server, whether it is Apache, IIS or other containers, the picture is the most consumption of resources, so we have to separate the picture and the page, which is basically a large web site will adopt the strategy, they have independent, and even many of the picture server. Such architectures can reduce the pressure on the server system that provides page access requests and ensure that the system does not crash due to picture problems.

   In the application server and picture server, can be different configuration optimization, such as Apache in the configuration of contenttype can be as little as possible to support, as few loadmodule, to ensure higher system consumption and execution efficiency.

6. Database cluster, library table hash

   Large Web sites have complex applications, which must use databases, and in the face of a large number of accesses, the bottleneck of the database can soon be revealed, when a database will soon be unable to meet the application, so we need to use the database cluster or library table hash.

   In the database cluster, many databases have their own solutions, Oracle, Sybase and so on have a good solution, the common MySQL provided by the Master/slave is a similar scenario, you use what kind of db, refer to the corresponding solutions to implement.

   The database cluster mentioned above is constrained by the DB type used in architecture, cost, and extensibility, so we need to consider improving the system architecture from the perspective of the application, and the library table hashing is the most common and effective solution.

   We install the business and application in the application or function module to separate the database, different modules corresponding to different databases or tables, and then according to a certain policy on a page or function of a smaller database hash, such as the user table, according to user ID for the table hash, This makes it possible to improve the performance of the system at a low cost and has a good scalability.

   Sohu Forum is the use of such a framework, the Forum users, settings, posts and other information database separation, and then to the post, the user in accordance with the plate and ID hash database and table, finally can be configured in the configuration file simple configuration will allow the system at any time to add a low-cost database to supplement the system performance.

8. Cache

   The word cache has been touched by technology, and caches are used in many places. Caching in the Web site architecture and Web development is also very important. Here we first describe the two most basic caches. The advanced and distributed caches are described later.

   Architecture cache, people familiar with Apache can know that Apache provides its own cache module, can also use the addition of Squid module for caching, both of which can effectively improve the access response of Apache.

   Web application development cache, the memory cache provided on Linux is a common cache interface, can be used in web development, such as Java development can call MemoryCache to some data caching and communication sharing, some large communities use such a framework. In addition, in the use of web language development, all kinds of languages have their own cache modules and methods, PHP has pear cache module, Java more,. NET is not very familiar with, I believe there is certainly.

10. Mirror

    Mirroring is often used by large web sites to improve performance and data security, the mirror technology can solve the different network access providers and geographical user access speed differences, such as the difference between chinanet and edunet prompted a lot of websites in the education network to build mirror site, Data is scheduled to be updated or updated in real time. In terms of mirror detail technology, this is not too deep, there are many professional ready-made solution architectures and products to choose from. There are also inexpensive ways to implement software, such as the tools of Rsync on Linux.

11. Load Balancing

    Load balancing will be a high-end solution for large web sites that address high-load access and a large number of concurrent requests. Load balancing technology has developed for many years, there are many professional service providers and products can be selected, I personally contacted a number of solutions, including two architecture can give you a reference.

    (1), Hardware four layer Exchange

    The fourth layer Exchange uses the header information of the third layer and fourth layer packets, according to the application interval to identify the business flow, the entire interval segment of the business flow distribution to the appropriate application server for processing.

    The layer fourth switch function is like a virtual IP, pointing to the physical server. It transmits services that comply with a variety of protocols, such as HTTP, FTP, NFS, Telnet, or other protocols. These operations are based on physical servers and require complex load balancing algorithms. In the IP world, the business type is determined by the terminal TCP or UDP port address, and the application interval in layer fourth switching is determined by the source and endpoint IP addresses, TCP, and UDP ports.

    In the hardware four-layer switching product area, there are some well-known products to choose from, such as Alteon, F5, etc., these products are expensive, but value for money, can provide very good performance and very flexible management capabilities. "Yahoo China" at the beginning of nearly 2000 servers, only the use of three or four alteon will be done.

    (2), software four layer Exchange

    When you know the principle of hardware layer four switch, the software four layer exchange based on the OSI model comes into being, so the solution achieves the same principle, but the performance is slightly worse. But to meet a certain amount of pressure or comfortable, some people say that the software implementation is actually more flexible, the ability to handle the full look at your configuration of the familiar ability.

    Software four-layer switching we can use the common LVS on Linux to solve, LVs is Linux Virtual Server, he provides a real-time disaster response based on the Heart Line heartbeat solution, improve the system robustness, At the same time, the flexible virtual VIP configuration and management functions can meet a variety of application requirements, which is necessary for distributed systems.

    A typical use of load balancing strategy is to build a squid cluster on the basis of software or hardware four-layer switching, which is adopted on many large Web sites including search engines, which have low cost, high performance and strong extensibility, and it is easy to add or subtract nodes to the architecture at any time.

    For large web sites, each of the previously mentioned methods may be used at the same time, here is relatively simple introduction, the implementation of a lot of details in the process need to be familiar with and experience. Sometimes a small squid parameter or Apache parameter setting can have a significant impact on system performance.

12. Latest: CDN Acceleration Technology

    What is a CDN?

    The full name of the CDN is the content distribution network. The goal is to add a new layer of network architecture to the existing Internet, publish the content of the site to the "Edge" of the network closest to the user, so that users can get the content they need and improve the responsiveness of users to the site.

    A CDN is different from mirroring because it is smarter than mirroring, or it can be used as a metaphor: cdn= more intelligent mirror + cache + traffic diversion. Therefore, CDN can obviously improve the efficiency of information flow in Internet network. From the technical comprehensive solution due to network bandwidth is small, user access is large, dot distribution is not equal problem, improve the response speed of users to visit the site.

    Types of CDN Features

    The implementation of CDN is divided into three categories: mirror, Cache, and leased line.

    Mirror sites (Mirror site), which are the most common, allow content to be published directly for static and quasi-Dynamic Data synchronization. However, the cost of purchasing and maintaining a new server is high, and a mirror server must be set up in each region with professional technicians for management and maintenance. For large web sites, the bandwidth cost of updating is also greatly increased.

    Cache, low cost, suitable for static content. Internet statistics show that more than 80% of users often visit the content of 20% of the site, under this rule, the cache server can handle the majority of the customer's static requests, and the original server only need to process about 20% non-cached requests and dynamic requests, thus greatly speeding up the response time of the customer request and reduces the load on the original server.

    CDN Services typically place cache servers on key nodes across the country.

    Dedicated line, allowing users to directly access the data source, you can achieve dynamic synchronization of data.

    Examples of CDN

    For example, when a user visits a website, the site uses global load balancing technology to direct users ' access to a cache server that is closest to the user's work and responds directly to the user's request.

    When a user accesses a website that has already used a CDN service, the most important difference between the parsing process and the traditional parsing method is that the site's authoritative domain name server does not respond to the local DNS resolution request in the traditional polling mode, but takes full account of the location where the user initiated the request and the current network situation. The decision to direct the user's request to a node cache server that is relatively light on the user's last load.

    Through the combination of user location algorithm and server health detection algorithm, the user's request can be directed to a cache server distributed on the edge of the network to ensure the user's access can be more timely and reliable response.

    Since a large number of user accesses are directly responded by the CDN Node cache server distributed at the network edge, this not only improves the user's access quality, but also effectively reduces the load pressure of the source server.

High Concurrency Website Solution