Chapter 1: Overall Architecture Diagram of High-Performance Web Macro-Architecture

The next few blog posts will bring you a relatively simple macro-architecture solution and detailed implementation and deployment tutorials. No pictures and no JB ---->

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

1. Nginx reverse proxy server (Nginx2, Keepalived2, yum source 1): All user requests are distributed through nginx reverse proxy, and the implementation is simple Load balancing (using sticky session method), through Keepalived to realize the active and backup relationship of nginx;

2. Application server (Tomcat2, ActiveMQ2, NodeJS2, Memcached2, Heartbeat2): Tomcat and nodejs use nginx for management and distribution, mq Use its own failover method to achieve disaster recovery, memcached uses heartbeat to manage dual-boot disaster recovery;

3. Relational database cluster (mysql2, Keepalived2): mysql is the main master and mutual backup, and Keepalived is used to achieve unified external access. , in this cluster mysql is a configuration database, managing user data, navigation data, etc. Why not use nginx? Let’s talk about it later

4. Hbase database cluster (NameNode2, Zookeeper3, JournalNode3, HMaster2, RegionServer4, DataNode4): There is no need to go into too much detail about the Hbase database cluster. I believe everyone has a certain understanding.

Next, let’s build this seemingly huge macro structure together. . . .

The above introduces the first chapter: the overall architecture diagram of high-performance Web macro-architecture, including all aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials.