simple load balancer

E-commerce Web site technology architecture with over 1 million visits The first introduction to E-commerce Web site high-performance, highly available solutions. From the frame composition of the scheme, the application is lvs+keepalived load balance. Achieve high-performance, highly available solutions (server clusters, load Balancing, high-performance, highly available, highly scalable server cluster)

many problems such as slow access speed of key applications, which brings a lot of trouble to users. The reason is simple. Because of the complexity and diversity of applications, especially the access to the Internet by enterprise intranet applications, the network is no longer as easy as interconnection. This is like urban transportation. If the optical path is well repaired, the problem cannot be solved. The Planning and Management of routes play

achieve load balancing. For example, if you want to use three web servers to respond to HTTP requests from www.ghq.net back and forth, you can set the DNS server for the domain to include the results similar to the following example: www1 in a 192.168.1.1 www2 in a 192.168.1.2 www3 in a 192.168.1.3 WWW in cname www1 WWW in cname www2 WWW in cname www3 external clients may randomly obtain different WWW addresses, then the subsequent HTTP request is se

one file. The benefits are simple, possibly as long as there are few configurations. However, as the number of servers increases, it becomes very difficult to monitor log files on each server. 2. Logging to a share this method is still available for each server, but they are stored on a central file server through a sharing mechanism, which makes monitoring logs easier. The problem with this scenario is that if the file server is unavailable, a

Now, basically all enterprises use the network for daily work. In the network operation of an enterprise, the transmission and data sending and receiving processes are not evenly distributed. Then, using Server Load balancer technology can achieve a balanced concept. So how to implement it? If it is not realistic to purchase large load balancing equipment, softwa

systems for such later users. Solution 2 analysis:Advantage: the Server Load balancer ("Server Load balancer" for short) makes full use of server resources to conveniently add new servers, which is transparent to clients.Disadvantage: the client may be connected to a server with low

machine. If the real situation is like this, it is understandable to do so. What if the situation is not so? The physical performance and configuration of each slave is not the same, and the use of random load balancing, regardless of performance, is very unscientific, which can bring unnecessary high loads to machines with poor machine performance, even the risk of downtime, while high-performance database servers do not fully perform their physical

addresses. Therefore, the client that queries this name will get an address, in this way, different customers can access different servers to achieve load balancing. DNS Server Load balancer is a simple and effective method, but it cannot distinguish between servers or reflect the current running status of servers. Wh

balancing software Load Balancing solution refers to installing one or more additional software on the operating system of one or more servers to achieve load balancing, such as DNS load balancing. It has the advantages of simple configuration, flexible use and low cost based on specific environments, and can meet gen

the cluster. Of course, the introduction of this concept undoubtedly increases the complexity and maintainability of the system. We have no way to escape. With Sub-databases, clusters, and Server Load balancer, is it all right? Things are far less simple than we think. Even with these things, we can basically ensure that our data layer can withstand a lot of pre

according to the weight in the cluster, a certain proportion of the load allocated to the DB server. Of course, the introduction of this concept has undoubtedly increased the complexity and maintainability of the system. There must be something lost, and we have no way to escape. With a sub-library, with a cluster, with a load balancer, is it all right? Things a