Why is Clean Architecture great for complex projects?
Milan Jovanović argues that Clean Architecture works especially well for complex, large‑scale applications. He notes that while it is not revolutionary, it gives clear guidance on how to structure code and offers promises like maintainability, testability, loose coupling, and separation of concerns. He uses it when he wants to apply Domain‑Driven Design, handle complex business logic, build highly testable projects, and enforce design policies through the architecture. He also describes both Clean Architecture and related approaches as domain‑centric, with the Domain at the core and use cases as a shared concept.
He takes a pragmatic stance, allowing himself to “break” Clean Architecture when it simplifies things, accepting that this may not be pure Clean Architecture but still provides most of its benefits. He advises ignoring critics who dismiss Clean Architecture, emphasizing that people operate in their own bubbles, and encourages engineers who see value in it and know how to write good software. He briefly mentions his .NET Weekly newsletter as a resource on .NET and software architecture.
Reading notes#
- Clean Architecture is described as well suited for complex, large‑scale applications.
- It is not presented as a revolutionary idea but as a prescriptive way to structure code.
- The author lists key promises: maintainability, testability, loose coupling, and separation of concerns.
- He chooses Clean Architecture when he wants to apply Domain‑Driven Design.
- Another use case is solving complex business logic.
- He also uses it to build projects that are highly testable.
- He relies on it to enforce design policies through the architecture itself.
- If these conditions match a project, he considers Clean Architecture an excellent option.
- He states that he tries to be pragmatic in applying Clean Architecture.
- Pragmatism, for him, includes the freedom to break Clean Architecture rules when that simplifies the system.
- He acknowledges that this pragmatic approach is not Clean Architecture in the purest sense.
- Even without purity, he believes he still gains most of Clean Architecture’s benefits.
- He describes Clean Architecture and a related architectural approach as revolving around the same idea.
- In both approaches, the Domain sits at the core and is treated as the principal part of the system.
- He groups them under the idea of “Domain‑centric architectures.”
- Both approaches are said to share the concept of use cases.
- He briefly agrees with someone that a mentioned concept is related.
- He promotes “The .NET Weekly” newsletter, focused on improving at .NET and software architecture, with 27,000+ subscribers.
- He advises readers not to listen to Clean Architecture haters, saying everyone lives in their own bubble.
- He claims that if you see value in Clean Architecture and can write good software, you will benefit strongly from it.
