Summary:
The book provides principles and guidelines for creating software architectures that are maintainable, scalable, and testable, independent of frameworks, databases, and user interfaces. It emphasizes the importance of separating concerns through layers and abstractions, and presents practical advice on how to apply these concepts to real-world software development.
Key points:
1. Dependency Rule: In clean architecture, dependencies should point from outer layers (UI, database) to inner layers (business rules) to keep core functionality stable.
Books similar to "Clean Architecture":
Pragmatic Programmer, The
Hunt Andrew|Thomas David
Domain-Driven Design Distilled
Vernon Vaughn
Pragmatic Programmer, The
David Thomas|Andrew Hunt
Domain-Driven Design
Evans Eric
Patterns of Enterprise Application Architecture
Fowler Martin
Implementing Domain-Driven Design
Vernon Vaughn
Microservices Patterns
Chris Richardson
Design Patterns
Gamma Erich|Helm Richard|Johnson Ralph|Vlissides John
Head First Design Patterns
Eric Freeman|Elisabeth Robson
Clean Code
Martin Robert C.