Programming

28152 readers

372 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

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

Is Clean Architecture actually good? What's your experience? (programming.dev)

submitted 3 weeks 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

[–] nous@programming.dev 1 points 3 weeks ago (1 children)

"Clean" Code, Horrible Performance offers a good argument against it purely from a performance stand point. Well worth a watch. But it also does not even make code easier to maintain. It just smears logic all over the place and makes it harder to understand what is going on. Trying to follow clean code principals just makes your code worse. And if you try to point that out to anyone they just say you are doing it wrong with no proper advice on how to actually improve things.

[–] somegeek@programming.dev 3 points 3 weeks ago

I'm not talking about the "clean code" approach. I'm talking about "clean architecture" for software design.

I have also heard things about how the multiple levels of abstraction in Clean Architecture can lead to worse performance, but we can always optimize the bottlenecks and skip the abstractions if needed. I also don't have any actual benchmark of how much is the performance hit.