Shulou(Shulou.com)05/31 Report--

This article mainly introduces "what is the evolution stage of web website architecture". In daily operation, I believe many people have doubts about what is the evolution stage of web website architecture. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts about "what is the evolution stage of web website architecture?" Next, please follow the editor to study!

The following stages can be used to understand the evolution of the website architecture.

1) stand-alone deployment

In the simplest case, you can put each process on the same server, just like we usually write programs.

Just a notebook, then each process runs on a PC, all right, just the basic functions.

May include: application server, file server, database server.

Problem: not enough memory, not enough hard drives, CPU competition.

How to solve?

2) Multi-machine deployment

In order to solve the above problems, put the application server, file server, and database server on three PC

Each does his own job, which solves the problem of competition among memory, hard disk and CPU.

The old problem has been solved, but there are still problems.

For a system, there may be a large number of access to databases, such as mysql databases

This can easily cause bottlenecks. What should we do? Then we have the following plan.

3) introduce the cache system

Who accesses the database, the application server

Well, I cache the data locally on the application server, or a special server acts as a remote caching server.

You should know that the fundamental difference between caching and database servers is that the former is a memory concept and the latter is a hard disk concept.

Access speed is not of an order of magnitude.

This solves the bottleneck of the database server.

Cache = local cache + remote cache

But there is a new bottleneck, a large number of visits, which makes the application server unbearable.

What shall I do?

4) Server cluster

Clusters can be introduced and multiple application servers can be deployed.

Through the load balancing mechanism, access sharing is handed over to each server to solve.

Even if the number of visits increases, I can only increase the number of application servers.

New problem, if the cache still does not satisfy the appetite of the application server

What should I do if I still need to access the server?

5) read-write separation of database server

In the previous scheme, the database server was responsible for all reads and writes.

Now the reading and writing are separated.

How do you separate reading and writing?

Master database server + slave database server.

When writing, write to the master server, the master server will synchronize with the slave server to ensure the consistency of the data.

When reading, read the slave server, does not affect the master server.

Here we need to ensure the immediacy of synchronization.

Consider slicing if necessary.

6) reverse proxy

If the reverse proxy server can provide the user's resources, it will be returned directly to the user.

Otherwise, submit it to the real server, which can be combined with load balancing.

7) introduce nosql mechanism

At present, there is a lot of demand for the network, and there will be more requirements for the background.

At this time, consider the introduction of nosql database, can effectively solve some of the problems.

8) Business split

Before only from the technical solution of some things, in fact, there are related to the business.

Split a website into subsystems, each of which is solved by a team and then spliced together.

It can be mashed by sharing databases, or message queues, and so on.

Maintain the relevance of subsystems.

Each subsystem executes in a distributed context.

9) add:

For example, for the database server, the master-slave mechanism can not solve the problem of master server downtime.

At this time, a server cluster should be introduced to ensure that after the master server goes down, there is a slave server rising to the master server.

Ensure that the system runs 24 hours from 365 to 24 hours.

Introduce distributed file systems and distributed databases if necessary.

At this point, the study on "what is the evolution stage of web website architecture" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.