this post was submitted on 24 Jul 2026
35 points (100.0% liked)

Programming

27857 readers
278 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
35
Is Clean Architecture actually good? What's your experience? (programming.dev)
submitted 3 days ago by somegeek@programming.dev to c/programming@programming.dev
23 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] eager_eagle@lemmy.world 12 points 3 days ago

IME it's an interesting read and some of the problems raised are valid, but the solutions are often unrealistic and overengineered. Same with design patterns, learn them to be aware of the problems, possible solutions, and their trade offs; but don't feel the need to warp the entire project around it.