The difference between architecture, framework and design pattern

Architecture, framework, and design patterns are all too familiar to those who work in IT. So what is the connection between the three? What's the difference?

Architecture: Architecture is a few verbs and a methodology that includes a series of activities and steps. You can think of architects, big data architects, software architects, chief architects, etc. Their job responsibilities are to build a set of frameworks through a series of steps based on their own knowledge (methodology).

Frame: A frame is a shelf and a noun. To solve or deal with complex problems, the construction of the framework requires the guidance of architectural methodology. If you understand the architecture, you can understand the framework.

Design pattern: In a certain environment, a solution to a certain type of problem. For example, the design patterns proposed by the Gang of Four provide the best solutions to common problems faced in the software development process. Learning these patterns helps less-experienced developers learn software design in a quick and easy way.

In general: Design Patterns > Architecture > Frameworks. If we insist on using a metaphor, we can use the metaphor of a house. The concept of design pattern is relatively broad, which can be understood as very simple principles, such as: houses cannot be built in low-lying areas (because they are easy to be flooded); It is built on the mountainside (because the scenery is good and the air is good) and so on. Architecture refers to all the planning of building a house. For example, if we want to develop a villa project, the architect of this project needs to consider factors such as where to build it, orientation, apartment type, construction period, price, etc. The last is the frame, which can be simply understood as using steel bars to build a shape, and adding cement and red bricks to it.

Guess you like

Origin blog.csdn.net/qq_44491709/article/details/114335179