Forum Discussion
Solved
Is clean architecture overkill for small teams maintaining a single web app ?
I've been exploring clean architecture and while I appreciate its separation of concerns and testability, I can't help but wonder, it is over for small teams ( say 2-4 devs) maintaining a single, rel...
For a small team with a stable web app, full Clean Architecture is usually overkill the extra layers and abstractions can slow you down more than they help. A lighter, “clean-ish” approach works best: keep business logic separate from framework/DB code, but skip unnecessary ceremony. This way you get testability and maintainability without sacrificing velocity.
Yes, it might become overkill for small teams working with a single application. Most importantly, if the business doesn't anticipate significant growth in requirements, there is no point in complicating things and making your life difficult when building the solution.