Book · 2017
Clean Architecture
by Robert C. Martin
Robert Martin's rule: business logic sits at the center of the system, frameworks and databases plug in at the edges, never the other way around.
What does Reddit think of Clean Architecture?
105 mentions in seven years, mostly as a footnote to Clean Code rather than a book anyone argues about on its own terms. The two cscareerquestions reading-list threads (↑687, ↑498) fold it into 'the whole Clean series' without distinguishing what it actually claims: that business logic should stay ignorant of frameworks and databases, not the other way around. Where r/programming does get specific, it's unflattering: the ↑134 comment says Uncle Bob 'talks in more absolutes than a Sith Lord,' backtracking only to admit the rule is aspirational, never fully reachable. r/ExperiencedDevs pushes back on a different misreading. The ↑71 comment separates the book from bad microservices decisions entirely, arguing a junior team's mistakes aren't 'clean architecture's' fault. Sentiment across the tracked subs leans positive but stays thin — not from dislike so much as thin engagement: almost nobody here is debating it. It shows up on lists. It doesn't show up in arguments.
Community feedback & reader fit
Themes
- · The dependency rule: business logic at the center, frameworks at the edge
- · A case-study extension of Uncle Bob's SOLID principles
- · Frequently blamed for microservices decisions it doesn't actually mandate
- · Read as a package deal with Clean Code, rarely on its own
- · An absolutist prescriptive style with real detractors
Common praise
- + cscareerquestions folds it into the standard 'whole Clean series' recommendation without much dissent.
- + r/ExperiencedDevs separates the book's actual argument from bad microservices decisions teams blame on it.
- + The dependency-rule framing gives people vocabulary for an architecture debate they were already having.
- + It's still the reference point cited when 'business logic ignorant of the framework' comes up as a design goal.
Common criticism
- − The ↑134 r/programming comment calls Martin's tone 'more absolutes than a Sith Lord,' and the thread doesn't really argue back.
- − 105 mentions across six subreddits over seven years means there's barely a debate to characterize.
- − cscareerquestions treats it as inseparable from Clean Code — both threads bundle the two books into one recommendation.
- − The cscareerquestions activity that recommends it is old; the sub's last tracked mention dates to 2022, even as r/programming and r/ExperiencedDevs kept discussing it into 2025.
Who it's for
Read this after Clean Code, not instead of it. Reddit treats the two as a set, not alternatives. If your team is already arguing about microservices boundaries, r/ExperiencedDevs would rather you separate that argument from this book's actual claim about dependency direction. Sith-Lord absolutism is a fair complaint if you're allergic to prescriptive style guides in general; the underlying rule holds up better than Martin's delivery of it. There isn't much discussion here to lean on either way — you're mostly evaluating the idea itself, not joining a live conversation about it.
Mentions over time
Which Reddit comments matter for Clean Architecture?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“Wordpress is NOT essential, and if you try to pursue that path too heavily you will limit your earning potential. Companies with enterprise products are … want to focus on front-end web dev, here's what I recommend: ### 1. Learn more than the language Learn the fundamentals of writing *good* softwar…
“The Pragmatic Programmer is like the cornerstone for code quality. As well as Clean Code. EDIT: I'm going to include a few more that I think will help for your career. * Clean Architecture by Robert C Martin (the whole Clean series is good) * Code Simplicity by Max Kanat-Alexander * Refactoring:…
“The hardest part about getting into the industry is breaking the can’t get a job <-> can’t get experience cycle. You’ve broken that cycle. It should get easier now. Forget about Machine Learning focus on the fundamentals. On one hand that means read books like “Clean Code”,“Clean Architecture”. Lear…
“We should really just put together a community reading/listening list... Reading: * Clean Code / Clean Architecture / […
“My guess is your colleagues don’t understand Clean Code, Clean Architecture or SOLID. It’s perfectly acceptable to build a monolith using these principles. Most of our projects use hexagonal architecture, which works really well for us. Great productivity and feature pace. Great maintainability. And…
“Yes, you can. I myself have only BA in Civil Engineering and managed to land a junior position after 1.5 years of self-learning. Apart from general knowledge about your programming language, before going to an interview you should know: * What is a thread, what is a process, how do they differ, do …
“This. Development is hard. With the growing popularity of bootcamps where you can be "a fullstack dev in 5 months!", people forgot that it is not so simple. How many devs know what are SOLID, FIRST tests, YAGNI, Clean Code, Clean Architecture, TDD... and practice them? My advice? Read books. For …
“As someone who owns clean code, clean agile, and clean architecture, uncle Bob does tend to talks in more absolutes than a Sith Lord. He’ll back track a bit by saying, it’s goal, you’ll never reach it, but you should always try. The internet has taught me that people really struggle with nuance, or…
“20+ years in. I make it a point to reread these books every couple of years. I've split them into 2 sections because it is not just about learning how to code, it is also about learning how to work with others. specifically about engineering 1. design patterns - 978-0-201-63361-0 2. clean architectu…
“There's no one resource, of course, but I've gotten a lot of really solid learnings about managing data at scale with Kleppmann's "Designing Data-Intensive Applications". I reference this one because how data is handled is probably one of the biggest jumps between frontend and backend. Edit: Anothe…
“I was in a similar spot and these fixed me up real good: * Clean Architecture * Domain Driven Design * Implementing Domain Driven Design * Patterns of Enterprise Application Architecture * Hexagonal Architecture * [Levels of Modularity](https:/…
“I don’t think microservices and clean architecture are related are they? It seems like your engineering team are a bit junior, but clean code and uncle Bob are not responsible for that. At least they are juniors, trying to follow good practices, that’s better than most…
“I would also add that "Clean Architecture" is a brand name and doesn't mean "clean/neat". It certainly sells books though, and who could argue with the word 'clean', you wouldn't want to be 'dirty', would you? Devil's in the details.
“I’ve only been a dev for 3 years and I went to a technical school. The thing I would change would be my old attitude about computer science books. For … written from experts. They’re comprehensive and encapsulated. Meaning they are one cohesive experience rather than random sites filling in holes..…
“This is how it's explained in chapter 2 of Clean Architecture: >I began to assemble them \[SOLID principles\] in the late 1980s... The final grouping stabilized in the early 2000s... In 2004 or thereabouts, Michael Feathers sent me an email saying that if I rearranged the principles, their first wor…
Convinced? Pick up Clean Architecture
Readers also mention
Books that share discussion threads with Clean Architecture — counted from the comments, not curated.
Clean Architecture — frequently asked
Is Clean Architecture as controversial as Clean Code?+
No — there isn't enough discussion for it to be controversial. 105 mentions across seven years is a fraction of Clean Code's volume, and most of them just bundle the two together as 'the whole Clean series.' The one pointed critique in the data, r/programming's ↑134 comment about Sith-Lord absolutism, is really aimed at Martin's writing style broadly, not this book specifically.
Does Clean Architecture actually cause microservices overuse?+
r/ExperiencedDevs says no. The ↑71 comment pushes back directly on blaming the book for bad microservices decisions, arguing a junior team's mistakes aren't 'clean architecture's' fault. The book's actual claim, decoupling business logic from frameworks and databases, doesn't mandate any particular service topology.
Should I read Clean Architecture before or after Clean Code?+
Reddit doesn't really sequence them — the cscareerquestions threads (↑687, ↑498) list both in the same breath as one 'Clean series' recommendation. Want code-level habits first? Start with Clean Code. Already past that and arguing about system boundaries? Clean Architecture is the more relevant one.
Is Clean Architecture worth reading in 2026?+
Probably, if the dependency rule is new to you, but temper expectations about finding community discussion to lean on. r/programming and r/ExperiencedDevs still mentioned it into 2025, but the total volume (105 mentions) means you're evaluating the idea on its own rather than joining an active debate about it.