Shulou(Shulou.com)06/02 Report--

This article mainly explains "what is the scalable exhibition architecture of web sites". The explanation in this article is simple and clear, easy to learn and understand. Please follow the ideas of Xiaobian slowly and deeply to study and learn "what is the scalable exhibition architecture of web sites" together!

Extensibility-The ability of a system to continuously expand or improve its functionality with minimal impact on existing systems. It is manifested in the stability of the system infrastructure, less dependence and coupling between applications, and agile response to changes in requirements. It is an open-close principle at the level of system architecture design (open for extension and closed for modification). The architecture design considers future functional extensions. When new functions are added to the system, there is no need to modify the structure and code of the existing system.

Scalability-The ability of a system to increase or decrease its ability to compute transactions by increasing or decreasing the size of its resources. If this increase or decrease is proportional, it is called linear scalability. In website architecture, it usually refers to the use of clustering to increase the number of servers and improve the overall transaction throughput of the system.

1. Build scalable website architecture

Low-coupling systems are easier to scale and reuse.

Modularization is the core idea of designing scalable architecture of web site, and on this basis, reduce the coupling between modules and improve the reusability of modules.

Layering and partitioning are not only scalable, but also important means of modular design. Software is divided into several low-coupling independent component modules by layering and partitioning, and these component modules are aggregated into a complete system by message passing and dependent invocation.

In large websites, these modules are deployed in a distributed manner, independent modules are deployed on independent servers, and the coupling relationship between modules is physically separated to further reduce coupling and improve reusability.

2. Using Distributed Message Queue to Reduce System Coupling 2.1. event-driven architecture

Event-driven architecture keeps modules loosely coupled by transmitting event messages between modules with low coupling, and accomplishes cooperation between modules through communication of event messages. A typical event-driven architecture is the producer-consumer pattern common in operating systems. In large Web sites, the most common means of implementation is distributed message queues.

2.2. distributed message queue

The message producer application pushes the message to the message queuing server through the remote access interface, and the message queuing server immediately returns a success response to the message producer after writing the message to the local memory queue. The message queue server searches for message consumer applications subscribing to the message according to the message subscription list, and sends the messages in the message queue to the message consumer applications through the remote communication interface according to the first-in, first-out (FIFO) principle.

In terms of scalability, because data on a message queuing server can be viewed as being processed on the fly, scalability design is simpler, similar to stateless servers. Add the new server to the distributed message queue cluster and notify the producer server to change the list of message queue servers.

In terms of availability, in order to avoid the problem caused by slow processing of consumer processes and insufficient memory space of distributed message queue servers, if the memory queue is full, the message will be written to disk. After the message pushing module finishes processing the memory queue message, the disk content will be loaded into the memory queue to continue processing.

3. Building reusable business platforms with distributed services

Distributed services decompose system coupling through interfaces, and different subsystems invoke services through the same interface description.

The requirements and characteristics of large-scale website distributed services:

Load Balancer

failover

Efficient telecommunications

integrated heterogeneous system

least intrusive for applications

version management

real-time monitoring

4. Scalable data structure

In order to ensure the correctness of relational operations, traditional relational databases need to specify the schema of the table-field names, data types, etc. when designing the database table structure, and to follow a specific design paradigm. These specifications pose a problem: it is difficult to meet the challenges of changing requirements, so some people have to design redundant fields in advance to meet them.

Many NoSql databases use the ColumnFamily design to design extensible data structures.

Thank you for reading, the above is "web site scalability architecture is what" the content, after the study of this article, I believe that we have a deeper understanding of the web site scalability architecture is what this problem, the specific use of the situation also needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!

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.