On architecture, framework and architect

Let's take a look at my personal views on the following two nouns:

Software Architecture:

The architecture of almost every software system is different, because the first step in software architecture is to make a technical decision based on the important requirements and constraints of the current project.

Software framework:

Can be divided into industry frameworks and common frameworks.

The common framework is a collection of modules (at the bottom + top level) that are commonly used in most software projects (at the same time exposing hotspots) to improve development speed and quality

An industry framework is a collection of software that extracts similar domain logic to encapsulate (simultaneously exposing hotspots) to a particular domain, improving development speed and quality

Industry frameworks can be based on a common framework.

From an architect's perspective, the development of architecture evolves into framework development (due to the need to consider reuse and developer-friendly API features)

Scalability: generally refers to the machine level of horizontal expansion, such as: Web server horizontal expansion, database read and write separation, the horizontal expansion of the middleware

Extensibility: Refers to when the requirements change, the system can easily be modified, extended.

Simplicity: The direct idea is AOP, because AOP enables developers to focus on business logic without having to think too much of the business logic code (such as logging, permissions, basic validation of parameters, etc.)

Performance: Related to scalability, algorithmic optimization, full utilization of CPU capacity

Because each project is different, the architecture is mostly different, but because people have limited energy, it is impossible to master everything, so when the schema is initialized, the unfamiliar

Schemas also require schema validation (as is the BVT of testers). Therefore, the individual learning ability, learning speed and practical ability are very important to the architect. So how do you do architecture validation?

1. Find the APIs provided by the Review review framework for several developers to see feedback, modify it, or fix it through technical training

2. Use AOP technology to insert the necessary logs, performance counters, memory footprint (and, of course, other technologies, not just AOP technology)

3. Performance test, performance analysis, or find technical testers to do

Finally, don't forget to do the technical training before the project, explain the principle of the framework and how to use it.

To sum up, the quality of the framework and architecture will seriously affect the user's efficiency, such as: the development of the developer efficiency, the architect is responsible for the important AH.

Attach an architectural Overview:

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Programming/project/