Chapter One: The overall architecture diagram of high-performance Web macro-architecture

The next few blog posts, bring you a simpler macro-architecture and detailed implementation of the deployment of the tutorial, no figure no JB---->

The above cluster environment is briefly described as follows (2 represents the number of services or software, i.e. there are multiple identical services):

1, Nginx reverse proxy server (NGINX2, Keepalived2, yum source 1): The user all requests through the Nginx reverse proxy to distribute, and realizes the simple load balance (uses the sticky session method), The main and standby relation of Nginx is realized by keepalived;

2, Application Server (TOMCAT2, ActiveMQ2, NodeJS2, Memcached2, HEARTBEAT2): Tomcat and Nodejs use Nginx to manage distribution, MQ uses its own failover way to achieve disaster tolerance, Memcached uses heartbeat to manage the implementation of dual-boot disaster recovery;

3, the relational database cluster (MYSQL2, Keepalived2): MySQL master mutual preparation, using keepalived to achieve unified external access, in this cluster MySQL is a configuration database, management user data, navigation data and so on. Why not use Nginx? I'll talk later.

4. HBase Database Cluster (NameNode2, Zookeeper3, JournalNode3, HMaster2, RegionServer4, DATANODE4): There's no need to be too burdensome about the HBase db cluster. I believe we all have a certain understanding.

Next, let's build this seemingly huge macro structure ....

The above describes the first chapter: a high-performance Web macro architecture of the overall architecture diagram, including the aspects of the content, I hope to be interested in PHP tutorial friends helpful.

