This article was published simultaneously on the official account: What things do mobile development:"The Way to Clean Architecture" - Reading Notes
"The Way to Clean Architecture" is a classic work by Robert C. Martin, which mainly revolves around how to design high-quality, maintainable and scalable software architectures. Its core view is
The essence of software architecture is never to pursue perfect technical implementation, but to maximize the maintenance and scalability of code while serving business needs through appropriate design.
1 Core objectives of architecture
- Extend system life (maintainable): Reduce technical debt and reduce maintenance costs
- Adapt to changes (scalable): Have the ability to continuously evolve and be able to flexibly respond to changes in demand and technological iterations;
2 Dependency rules
Design must followDependency inversion rules: High-level modules should not rely on low-level modules, but on abstraction. Commonly, decoupling the system hierarchy through dependency inversion and interface isolation, enhancing the flexibility and testability of code;
3 Hierarchical architecture
Through a hierarchical model (concentric circle model), the architecture is divided into multiple levels: core business logic -> use cases -> interface adapter -> framework tools, thereby ensuring that the business logic will not be invaded by the underlying technical framework and increasing the portability of the code;
4 Software Design Principles
When designing, follow the SOLID principle
- Single Responsibility Principle: Each module has only one reason for change:
- Opening and closing principle: the system is open to extensions and closed to modifications;
- Rich's rule principle: subclasses can replace parent classes without affecting correctness;
- Interface isolation principle: The interface should be fine-grained to avoid unnecessary dependencies
- Dependency inversion principle: both high-level and low-level modules should rely on abstraction
5 Component construction and architecture implementation
- Component design: Components are the smallest deployment unit of software, generally following the principle of dependency-free ring, stable dependency principle, and stable abstraction principle;
- Architecture model selection: According to business needs, select the appropriate hierarchical architecture, event-driven architecture, and microservice architecture to ensure that the system structure is clear and easy to maintain;
6 Architecture Evolution
An ideal architecture should have certain flexibility, which can not only meet current needs but also adapt to future changes, and ensure that the system technically delivers value in its life cycle through gradual reconstruction and debt management;
The way to clean code: the professional quality of programmers