US software architecture lies in simple, easy to use, stable, clear positioning function, the code is simple, easy to understand

1. The software architecture is required to master a learning costs, to learn too tired, too hard, too much to ask the rules, the threshold is too high, this architecture to make people suck too, and the promotion of little significance .

 

2. General a few technical staff to work in a company 3 --4 years, water flows downwards with the flow, so the software architecture also needs to take full account of these mobility problems, so that the losses caused by reduced mobility the minimum is better.

 

3. Good architecture, generally through practical work extracted out of thin air architecture software architecture often can not withstand the test, we need to go a long way to mature and stable, even if we do not pursue powerful multi-function , how high efficiency, at least the pursuit of stable, do not mistake here today, there tomorrow mistake, today lost this data, the data is lost, then it'll be too suck.

 

4. Too many features that can be realized too complex, universal architecture, tend to be a monster, after poor maintenance, poor improved, modified here, affecting where these improvements, there is unstable, it is best Some simple positioning function, which is specifically suited to one aspect, which specializes in one aspect of the process, lightweight better.

 

The technology continues to improve, the times are changing, architecture, too, need to change with the times, the language may be updated, update the database, updated ideas, so it can not expect too much hanging on a framework.

 

6. mature software architecture, not the final outcome Playing with technology, but extracted from the actual project the essence, the core purpose of the project, to better products and more reasonable, rather than the technology to play more high level.

 

7. Do not know which features into the architecture, the overall positioning architecture is what, a clear division of positioning modules do not know, and that was honestly do projects, improve your own basic skills, a few years, then toss, or direct others to learn about the essence of architecture, multi-reference, study more, than they could toss a blind better.

 

 

 

 

Reproduced in: https: //my.oschina.net/iwenr/blog/227651

Guess you like

Origin blog.csdn.net/weixin_34254823/article/details/91675079