The beauty of software architecture lies in its simplicity, ease of use, stability, clear functional orientation, concise code and easy to understand.

1. Proficiency in software architecture requires a learning cost, too tiring, too difficult, too many rules, too high barriers, this architecture is too annoying, the significance of promotion is not great.

two。 Generally speaking, a technician seldom works in a company for 3-4 years, and people go up and water flows down, so the software architecture also needs to fully consider these personnel mobility problems, so it is better to minimize the loss caused by personnel mobility.

3. A good architecture is generally extracted from practical work, and the software architecture of the architecture out of thin air often cannot stand the test, and it still takes a long way to become stable and mature. even if we do not pursue how strong the function is and how efficient it is, at least pursue stable operation, don't make mistakes here today, make mistakes there tomorrow, lose this data today, and lose that data tomorrow, that would be too annoying.

4. There are too many functions that can be realized, and the omnipotent architecture is often a behemoth, which is difficult to maintain and improve in the future, modified here, affected there, improved these, and became unstable there, and the best functional positioning is simpler, that is, it is specially suitable for which aspect to do, good at dealing with which aspect, lightweight is better.

5. The technology is constantly improving, the times are constantly changing, and the architecture is the same. with the change of the times, we may update the language, database, and ideas, so we can't count on an architecture to hang too much.

6. Mature software architecture is not the final achievement of playing technology, but the essence extracted from the actual project. The core purpose is to make the project better and more reasonable, not to play the technology to a higher level.

7. Do not know which functions are put into the architecture, what is the overall positioning of the architecture, the clear division of labor positioning of functional modules do not know, that is to honestly do the project, improve their own basic skills, and then toss about in a few years, or directly learn the essence of other people's architecture, more reference, more learning, may be better than their own messing around.

Rights management, workflow management to achieve my ability to the extreme, a person can only do so few things.