What are the common software architectures?

10 Common Software Architecture Patterns

Do you want to know how to design a large enterprise system? Before developing the main body of software, we must choose a suitable architecture to provide the required functions and quality characteristics. So before applying it to design, we should understand different architectures.

What is an architectural pattern?

Wikipedia: Architecture pattern is a universal and reusable solution to solve common problems in a given software architecture environment. Architecture pattern is similar to software design pattern, but its scope is wider.

In this article, I will briefly explain the application, advantages and disadvantages of common architecture patterns in 10.

1. classification mode

2. Client-server mode

3. Master-slave mode

4. Pipeline filtration mode

5. Agent mode

6. Point-to-point mode

7. Event bus mode

8. Model-view-controller mode

9. Blackboard mode

10. Interpreter mode

1. classification mode

This pattern is used to build a program that can be decomposed into groups of subtasks, each subtask is in an abstract layer, and each layer provides services for the previous higher layer. The most common four-tier system in general information systems is as follows.

Presentation layer (also called UI layer), application layer (also called service layer), business logic layer (also called domain layer), data access layer (also called persistence layer), application scenario, general desktop program, e-commerce web page program.

2. Client-server mode

The model consists of two parts: a single server and multiple clients. The server component provides services for multiple client components. Clients request services from the server, and the server provides corresponding services to these clients. In addition, the server continues to listen for client requests.

Application scenario

Online applications such as e-mail, document sharing and banking.

3. Master-slave mode

The model consists of two parts: master node and multiple slave nodes. The master node component assigns tasks to multiple independent slave node components, and calculates the final results according to the results returned from the slave nodes.

Application scenario

Database replication, the master database is regarded as the authoritative source and synchronized with the peripheral devices (master-slave drivers) connected to the computing system from the database.

4. Pipeline filtration mode

This pattern is used to build a system for generating and processing data streams. Each processing step is encapsulated in a filter assembly. The data to be processed is transferred to a pipeline, which can be used for buffering or synchronization.

Application scenario

Compilers with continuous filters perform the workflow of semantic analysis, syntax analysis, semantic analysis and code generation biological data procedures.

5. Agent mode

This pattern is used to build a distributed system with decoupling components. These components interact with each other through remote calls. The proxy component is responsible for the communication coordination of multiple components, and the server exposes their capabilities (services and characteristics) to the proxy; The client obtains the service from the proxy, and then the proxy redirects the client to the appropriate service in the registered service library.

Application scenario

Message queuing software, such as Apache ActiveMQ, Apache Kafka, RabbitMQ and JBoss Messaging.

6. Point-to-point mode

In this mode, each independent component is called a peer. A peer can obtain services from other peers as a client or provide services to other peers as a server. Peers can act as clients, servers, or both, and switch roles dynamically at different times.

Application scenario

File sharing networks, such as Gnutella and G2 multimedia protocols, such as P2PTV and PDTP private media programs, such as Spotify.

7. Event bus mode

This mode mainly deals with events and has four main components: event source, event listener, channel and event bus. The event source publishes the message to a channel on the event bus, and the listener subscribes to a channel and knows the message published in the subscribed channel.

Application scenario

Android development notification service

8. Model-view-controller mode

This mode, also called MVC mode, divides the interactive program into three parts: a model containing core functions and data, a view for displaying information to users (multiple views can be defined), and a controller for processing user input. It is realized by dividing the internal statement, presentation and acceptance of user information, decoupling components and allowing efficient code reuse.

Application scenario

World Wide Web programming framework of mainstream programming languages, such as Django and Rails.

9. Blackboard mode

This model is very useful for problems without deterministic scheme strategy. Blackboard mode consists of three main components: the global memory of blackboard structure containing solution space objects, the special module of knowledge source with self-contained representation, and the module of controlling component selection, configuration and execution. All components can access the blackboard, and new data objects can be generated and added to the blackboard. In the blackboard, some types of data can be found according to the matching rules of existing knowledge sources.

Application scenario

Speech Recognition, Vehicle Recognition and Tracking Interpretation of protein Structure Recognition Sonar Signal

10. Interpreter mode

This pattern is used to design components that interpret programs written in a specific language. This component mainly specifies how to evaluate program code lines, that is, to use a certain language [tag: content].