Chapter 1: Overall architecture of high-performance Web macro architecture

: This article mainly introduces the first chapter: the overall architecture of the high-performance Web macro architecture. if you are interested in the PHP Tutorial, refer to it. The following blog posts will provide you with a relatively simple macro-architecture solution and detailed implementation and deployment tutorials.

The preceding cluster environment is described as follows (2 indicates the number of services or software, that is, multiple identical services exist ):

1. Nginx Reverse proxy server (Nginx2, Keepalived2, and yum source 1): all user requests are distributed by nginx Reverse proxy, it also implements simple load balancing (using sticky sessions) and implements the master-slave relationship of nginx through Keepalived;

2. Application Servers (Tomcat 2, ActiveMQ2, NodeJS2, Memcached2, and Heartbeat2): Tomcat and nodejs use nginx for management and distribution, and mq uses its own failover method for disaster tolerance, memcached uses heartbeat to manage and implement dual-start disaster tolerance;

3. relational database cluster (mysql2 and Keepalived2): mysql is the master and slave nodes, and Keepalived is used for unified external access. in this cluster, mysql is a configuration database that manages user data, navigation data. Why not use nginx? Later

4. Hbase database clusters (NameNode2, Zookeeper3, JournalNode3, HMaster2, RegionServer4, and DataNode4): There is no need to worry too much about Hbase database clusters. I believe everyone knows this.

Next, let's build this seemingly huge macro-architecture together ....

The first chapter describes the overall architecture of the high-performance Web macro-architecture, including some content. I hope that my friends who are interested in PHP tutorials will be helpful.