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

The word "architecture" is a very common word for programmers. When it comes to architecture, most technicians will have an unattainable and very tall feeling. In fact, architecture is beside us, something we can see and touch.

Let's start by looking at a few concepts, the relationships and differences between systems and subsystems, modules and components, frameworks and architectures.

Systems and subsystems A system is a group of interrelated individuals operating according to specified rules to accomplish tasks that cannot be accomplished by individual elements alone. For example: the relationship between the automobile and the engine, tires and other components. A subsystem is also a system. It is consistent with the definition of a system, but it is observed from a different angle. A system may be a subsystem of a larger system. Modules and components are components of the system, but the system is split from different angles; from a logical point of view, it is "module", and from a physical point of view, it is "component"; the main purpose of dividing modules is to separate responsibilities, and the purpose of dividing "components" is to reuse units. Frameworks focus on specifications and functional products, such as the MVC specification and SpringMVC, the MVC development framework; Architecture focuses on "structure," which is the top-level structure of the system.

Summary: The system is divided into modules according to business or function, and some modules may be upgraded to subsystems; modules may use many components to achieve specific functions; at the same time, certain frameworks may be used as the basis for development, and architecture describes how various subsystems or modules work together.

Why Architecture? ** The main purpose of architecture design is to solve the problems caused by the complexity of software systems **

What are the main sources of complexity? Its main sources are as follows

1) High performance

2) High availability

3) Scalability

4) Low cost

5) Security

6) Scale

That is to say, architecture design exists to solve some key problems, and not every system needs architecture design.

When doing architecture design, you should not be greedy and complete, but follow a few simple principles.

1) Principle of suitability: suitability is better than industry leadership

Trying to do the work of so many people without so many people is the first major cause of failure; trying to reach the top without so much accumulation is the second major cause of failure; and dreaming of a flash of genius without that amount of excellent business scenario is the third major cause of failure.

2) Principle of Simplicity: Simplicity is better than complexity

Simple structure, simple logic

3) Evolution principle: evolution is better than one step

For architecture, eternity is the theme; for software, change is the theme.

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.