Solid principle

In terms of software architecture design , There is a general principle that cannot be bypassed , That's it SOLID principle . The general principle consists of the initials of five principles , They are as follows ：

• Principle of single responsibility （The Single Responsibility Prinlciple）： Any software module should only be responsible for a certain kind of behavior
• Opening and closing principle （The Open/Closed Principle）： Well designed software should be easy to extend , At the same time, it resists modification
• Richter's principle of substitution （The Liskov Substitution Principle）： If you want to build software with replaceable components , Then these components should follow the same interface , So that they can freely replace each other
• Interface isolation principle （The Interface Segregation Principle）： Unnecessary dependencies should be avoided in design
• Dependency Inversion Principle （The Dependency Inversion Principle）： Depend on abstraction rather than concrete

Build a good software system , We should not only focus on the implementation level of the code , Pay more attention to the design of the overall architecture . A good architecture design can avoid most of the bug, Cope with endless modifications and functional overlays . How to measure the quality of an architecture ？ An important criterion is its maintainability . As a small change, you need to change a lot of code , When you ask some unexpected questions , Such architecture design must be bad . Secondly, readability . The code is to be read , Chaotic architecture will complicate the logic of the code , Increase the difficulty of understanding .
In order to design a good architecture ,SOLID principle Through a series of principles to guide us How to correctly organize functions and data into components , And how to summarize these components into the final software .