Clean Architecture (CA) has become a widely adopted and beloved standard in the development community. Even if it doesn’t make much sense to use it in some cases, every developer should get familiar with it. At the end of the day, what dominates the industry almost always becomes the rule, regardless of whether you agree or not.
Even for simple CRUDs
Throughout my career, I’ve always worked on projects with over-engineering—projects that were just 4 pages of tables with CRUD operations but had multiple layers of abstraction. That’s why I advise: don’t rely on simple solutions for personal or small projects; instead, use what is dominant in the industry, like Clean Architecture. When you really need it, you’ll be ready to perform with over-engineering or even pass a tough interview.
The value of what is socially dominant
The main point is: it’s not just about what makes technical sense, but also about what is socially dominant in the industry. Learning and mastering Clean Architecture means you’ll be prepared for when your manager throws you into a sprint board with dozens of tasks in a system full of over-engineering and tight deadlines.
Mastering is better than resisting
Even if you are building a simple CRUD in .NET, it’s worth structuring the project following Clean Architecture. This way, you gain practical experience with something that challenges developers of all levels.
Ready for any challenge
Once we tackle a complex feature within a system using Clean Architecture, we soon deal with responsibilities of each layer, such as making a user entity in the domain work with Identity and EF Core without making the domain layer depend on NuGet packages. The earlier we solve these challenges, the less stuck we get in the future.