Site Background Architecture Understanding (i)

Recently contacted the Internet site architecture, Architecture evolution, development, etc.,

Just learning, now do a simple understanding, and

First, the background of the site commonly used lamp architecture,

System:linux/unix refers to, commonly used in Centos,debian,redhat,suse,

Storage:mysql Open Source relational database, extensible to memcached-distributed memory object cache system, maintains a unified hash table in memory, can store data in various formats: pictures, videos, files and database retrieval results. The hash table is stored in the Key,vaual kv value, and the remainder is calculated by dividing the number of hashcode by array, and the corresponding array of KV values can be found in the remaining number.

Service: There are five main types of Web service, including Apache,iis,lighttpd,zeus,nginx,... Apache has an open source web Service in 72% markets worldwide, with 49% of the top 100 in the U.S.

Script:php,perl,python and other explanatory scripting languages

Currently, 61% of the top 200 sites in China use the lamp architecture

Based on B/s web three layer system (layered design): client/Management side, Application server, data server, simply speaking is: Presentation Layer-Content presentation layer, application Layer-business logic processing, data layer-data management, storage and so on.

b/S portal site, various types of websites such as:

Ii. Building the architecture of the lamp-based medium-sized web site

1. Simplest single web+db architecture 10W pv-Web site page views per day website architecture

The following diagram:

2. Load balancer server, multi-Web server, cache server, DB server (master, slave read/write separation)

100W PV Website Architecture

The following diagram:

Load Balancer Server---

3.1000W PV Website Architecture

Load balancer Server, CDN Proxy Server, reverse proxy server, static resource server, distributed cluster, cache server, DB connection pool, multiple slave servers, DB master redundant backup,

The following diagram:

Other requirements include Message Queuing, distributed file systems, persistent cache systems, database slicing: horizontal and vertical, distributed deployment, reduced module coupling, and independent service for basic modules, such as user systems. Sub-tables, sub-Libraries

Site Background Architecture Understanding (i)