cross-posted from: https://programming.dev/post/54023908
Hi!
I’ve never read any of Uncle Bob’s books. But I have taken interest in “Clean Architecture” as it seems like a good solution to make mid to large sized projects simple to understand and maintain.
I think MVC gets too much coupling and fails at larger projects, same with n-tier. But I’m not sure about anything right now (software design is a very complicated problem after all).
So I was wondering if you friends who have used Clean Architecture in production can share your knowledge and experience with me about this design?
Is it actually good and worth investing in?
Footnote:
I’m especially weighing this architecture because Uncle Bob’s writings are really hit and miss. I don’t see him as a master or guru so I take everything he says with a grain of salt.
Anecdotally, from a programming support community I hang out in…
i’ve never seen anyone promote the values of Clean Architecture in the practical world. The only reason I even know about it, really, is because it’s a pretty popular topic for amateur/beginner developers to come in and ask about, because they read a book or a blog article about it, or are being taught about it in a class. And the response is always, universally, “Don’t use Clean Architecture, use Vertical Slice Architecture.”
I get the vibe that it’s been popularized in the same pattern as microservices or lambda functions: someone at a super-scaled company like Google or Amazon published a blog post about it, and how it works for them for some niche scenario, and everyone latched on to it as trendy, despite the fact that their scenarios are NOTHING alike