Typical architecture patterns for major software types

Type of software	Schema Mode	features and uses
system software	layering (layer)	observing systems from different levels, objects that deal with different levels of problems are encapsulated in different layers
	Pipes and Filters (Pipes and Filters)	Observing the system with the data flow viewpoint, the whole system consists of some pipelines and filters, the data that needs to be processed is piped to each filter, and each filter is a processing step. When the data passes through all the filters, all the processing is done and the final result is obtained. The pipeline model of the UNIX operating system is built on this architecture; when developed under UNIX, each process is a filter, and we can connect the process through the pipeline, allowing all the filters to complete the task in collaboration. The compiler for most programming languages is also based on this architectural pattern.
	Blackboard (Blackboard)	In this architecture, there are two different components, one is the central data structure that represents the current state, and the other is a set of independent artifacts that manipulate the central data. This architecture is primarily used for the development of databases and artificial intelligence systems.
Distributed software	Brokers (Broker)	In this architecture, the customer and the server communicate through a broker part, and the broker coordinates the operations between the client and the server. and send request and result information for customers and servers. Broker is a typical application of broker mode.
	Client/server (Client/server)	The system is divided into customers and servers, the server has been in the state of listening, the customer master active connection server, each server can serve multiple customers.
	Point-to-point (peer to peer)	The nodes in the system are all equal, and each node can connect to other nodes. In this architecture, it is generally necessary for a central server to complete the operations of discovering and managing nodes. Most of the applications of our familiar ICQ programs and Web service technologies are typical point-to-point structures.
Interactive Software	Model-View-controller (Model-view-controller)	When the user interface of the application is very complex, and the requirements of the user interface are easily changed, we can abstract the interaction type software into three kinds of component units, the model, the view and the controller, which can well separate the user interface and business logic and adapt to the changing demand. Most modern interactive software conforms to the characteristics of this architecture model in a certain program.
	Display-Abstract-controller (Presentation-abstraction-control)	This is another variant of the show-abstract-controller pattern, which is not described in detail here.

The final goal of the design is to maximize the implementation of code reuse, if you cannot reach the target of the reuse code, there is no need to extract the new class, (attribute is, some common relatively small code, so there is no need to attribute to the proposed to become a class.) If more than one class calls it, you can propose a new class).

Typical architecture patterns for major software types