41 books
—
19 voters
Goodreads helps you keep track of books you want to read.
Start by marking “Clean Architecture” as Want to Read:
Clean Architecture
by
Building upon the success of best-sellers The Clean Coder and Clean Code, legendary software craftsman Robert C. "Uncle Bob" Martin shows how to bring greater professionalism and discipline to application architecture and design.
As with his other books, Martin's Clean Architecture doesn't merely present multiple choices and options, and say "use your best judgment": it tel ...more
As with his other books, Martin's Clean Architecture doesn't merely present multiple choices and options, and say "use your best judgment": it tel ...more
Friend Reviews
To see what your friends thought of this book,
please sign up.
Reader Q&A
To ask other readers questions about
Clean Architecture,
please sign up.
Popular Answered Questions
Steve Fenton
The book is available now - both in paperback and digital editions.
Ilyes Hachani
The book is available now. No need for an early access version.
Community Reviews
(showing 1-30)
I really liked this book but also was a bit disappointed by it. I'm a huge fan of Robert Martin's work, I've read his previous books and I love Clean Code and The Clean Coder. Based on the title and artwork I had kind of assumed that this was just the next step of the Clean Trilogy, this time focusing on architectural concerns.
It is kind of that, but it's mostly not quite that. Really, this book is a lot of background information to understand the "meat" of the book, and the meat of the book is ...more
It is kind of that, but it's mostly not quite that. Really, this book is a lot of background information to understand the "meat" of the book, and the meat of the book is ...more
First of all, I’m a big fan of Robert C. Martin’s work. I think cleancoders.com (I have purchased all videos from Clean Code, Clean Coders and Clean Coders Applied series) is a great learning resource and I have read all others books (Clean Code, Clean Coders and Agile Software Development Principles, Patterns and Practices).
About this book, I may had too high expectations about this book. I’m disappointed. 85% of the book is reviewing the SOLID principles and how to apply them to components (it ...more
About this book, I may had too high expectations about this book. I’m disappointed. 85% of the book is reviewing the SOLID principles and how to apply them to components (it ...more
This is the first book of Uncle Bob that I didn't like – it's shallow, impractical, and full of stories from forgotten 90's. A significant part of the book (explanation of SOLID principles) has been copied (with few alternations) from "Agile PPP" book, which is, in my opinion, a much more thorough book.
To understand modularity patterns mentioned in this book, I suggest taking alternative path – reading "Java Application Architecture" by Kirk Knoernschild.
In addition to modularity and SOLID, the ...more
To understand modularity patterns mentioned in this book, I suggest taking alternative path – reading "Java Application Architecture" by Kirk Knoernschild.
In addition to modularity and SOLID, the ...more
Clean Guide for an Architect
The book covers different sides of the Software Architect role. The conflicting collaboration of business and technology. The crucial architect's focus topics. The architecture principles derived from the famous SOLID principles and proven by decades. Some of the common architecture mistakes.
All topics of the book have bright and laconic descriptions. The are also many colorful and didactic examples to the ideas, often taken from the author's experience. And besides, ...more
The book covers different sides of the Software Architect role. The conflicting collaboration of business and technology. The crucial architect's focus topics. The architecture principles derived from the famous SOLID principles and proven by decades. Some of the common architecture mistakes.
All topics of the book have bright and laconic descriptions. The are also many colorful and didactic examples to the ideas, often taken from the author's experience. And besides, ...more
Interesting, but too long with too many not needed and off-topic anecdotes. Still worth your time, but not as insightful as previous titles from "Clean X" series.
Some key remarks I have:
1. Even if it may look (at some point) deceptively simple, ... it isn't. In fact, the most valuable lessons will be truly comprehensible (& clear) only for people with certain level of experience.
2. This book doesn't try to cover anything in particular in the end-to-end way, it's more about certain aspects of software architecture Uncle Bob finds most important (e.g. SOLID principles, boundaries, proper approach to composition, etc.). Needless to say - these are unive ...more
1. Even if it may look (at some point) deceptively simple, ... it isn't. In fact, the most valuable lessons will be truly comprehensible (& clear) only for people with certain level of experience.
2. This book doesn't try to cover anything in particular in the end-to-end way, it's more about certain aspects of software architecture Uncle Bob finds most important (e.g. SOLID principles, boundaries, proper approach to composition, etc.). Needless to say - these are unive ...more
Many of the reviewers who rated it low misunderstood the book. I see in the reviews that they expected microservice, CQRS and other "architecture" descriptions. But this book is about something different. This is about the "clean" architecture. Yes he uses SOLID to describe architecture components, but from the different angle than talking about the code.
The book also is a good read just because of the style and story. Uncle Bob always is a good storyteller.
Just read and enjoy the book. Do not e ...more
The book also is a good read just because of the style and story. Uncle Bob always is a good storyteller.
Just read and enjoy the book. Do not e ...more
Interesting and very well written. If you are familiar with the SOLID principles, this book will be an easy read.
Not 5 stars because it contains too little information in my opinion. I don't mean that it is a short book, not at all. However it doesn't really revolutionize your perspective on design and architecture if you are already applying SOLID in you application.
In many places I had the distinct feeling that the author was talking in generic terms and just filling in the pages with non-esse ...more
Not 5 stars because it contains too little information in my opinion. I don't mean that it is a short book, not at all. However it doesn't really revolutionize your perspective on design and architecture if you are already applying SOLID in you application.
In many places I had the distinct feeling that the author was talking in generic terms and just filling in the pages with non-esse ...more
Really enjoyed it, it was surprisingly easy to read. Explained all the rules and principles well. I was thinking about our production code all the time while reading it.
Chapter about decoupling tests via a Test API really needs some examples. Especially because of already existing controversy about fragility of TDD etc.
Chapter about decoupling tests via a Test API really needs some examples. Especially because of already existing controversy about fragility of TDD etc.
Mixed feelings about this book. On one side, it explains what software architecture is about, filled with valuable design principles (at class level and at component level).
On the other side, it's a very short book, basically with a fast compilation of everything he said before. Even when he touches fresh subjects, like distributed systems (SOA/Microservices), the chapters are a little bit shallow. I've missed more code samples to clarify some concepts.
Don't get me wrong: it's a very good book, ...more
On the other side, it's a very short book, basically with a fast compilation of everything he said before. Even when he touches fresh subjects, like distributed systems (SOA/Microservices), the chapters are a little bit shallow. I've missed more code samples to clarify some concepts.
Don't get me wrong: it's a very good book, ...more
A review of programming paradigms and SOLID, adding very little more and simplifying the concept of architecture to only software architecture/design.
Chapter 34, authored by Simon Brown, is very good.
Chapter 34, authored by Simon Brown, is very good.
I think if a software engineer reads only two books in their career... first of all, shame on them :)... but second of all, those books should be 1) Clean Code, and 2) Clean Architecture.
MUSTREAD
and
MUSTREREAD
and
MUSTREREAD
It's an OK book. Not a total waste of your time but it's just Uncle Bob trying to milk the SOLID cow a bit more.
The book isn't bad, but not very practical.
All the principles described in the book make sense once you understand them and saw issues in practice. But what if you unfamiliar with them? What if you want to understand them? In this case, the book wouldn't help: the chapter dedicated to design/architecture principles are very short without any practical examples.
Lack of examples is the main problem though. It is hard to provide good samples for a design/architecture book but without them, it is ha ...more
All the principles described in the book make sense once you understand them and saw issues in practice. But what if you unfamiliar with them? What if you want to understand them? In this case, the book wouldn't help: the chapter dedicated to design/architecture principles are very short without any practical examples.
Lack of examples is the main problem though. It is hard to provide good samples for a design/architecture book but without them, it is ha ...more
I'm very disappointed with this book. I had very high expectations of it after having read Uncle Bob's excellent "Clean Code" and "The Clean Coder", but after reading this, I can only feel that my money's only purpose was to help the author set up a second gold-coated swimming pool at their mansion - there was little to learn here.
I would divide the book in two halves. The first of these hardly bears any relevance at all - it's mostly anecdotes and stuff that (in my opinion) doesn't really need ...more
I would divide the book in two halves. The first of these hardly bears any relevance at all - it's mostly anecdotes and stuff that (in my opinion) doesn't really need ...more
The book starts from the premise that design and architecture are the same, thus every decision you take from lower to the highest levels are a continuum of architectural decisions.
The book introduces you to the principles by which all of the these architectural decision should be taken - from classes(SOLID) to components(CCP,SDP,REP) and then to higher level architecture (layers).
It explains which elements of the software are architecture and which are mere details.
This book is not about specif ...more
The book introduces you to the principles by which all of the these architectural decision should be taken - from classes(SOLID) to components(CCP,SDP,REP) and then to higher level architecture (layers).
It explains which elements of the software are architecture and which are mere details.
This book is not about specif ...more
This is a book on architecture with context. Robert Martin explains an approach to architecture in a way that is grounded in good design and in history. Of the many points I took from the book, are ones that are both obvious, and insightful: ones that you never hear people talk about, but which I could not help agree with: Architecture is about what decisions you can defer, architecture is about creating a framework that makes change easy, and architectural choices go in cycles (there isn't a wh
...more
It is a lightweight read that touches on the basics of the Clean Architecture that Uncle Bob has been preaching over the years, a summary of all the blog posts and videos and his previous books. Clean Architecture is a way to describe a set of architectural ideas in software development, heavily influenced by Grady Booch, Ivar Jacobsen (BCE), Ports and Adapters, Hexagonal, VIPER etc. It is possibly the best way to create software products. A highly recommended read, along with Clean Code, Agile
...more
I thought the content was rather thin given the topic. Chapters were very short with very little actual code examples. If "Clean Code" tended to have too much code in it, this was the opposite. Architecture is most important for large projects, so it is difficult to include realistic code samples. Nevertheless, I think an example of refactoring a poorly architectured project into a well architectured one would have been useful. The Appendix was much longer than any chapter, but was pretty much a
...more
Great book. Software architect is important but from what I've seen, it hard to understand (That's why I don't think this book can receive 5 stars rating). That's why many software companies don't put it on the checklist. Cause software can work without a good architect.
A feature can be added to a well-architected software, costing 1 day and $1000. For bad architected software, the same feature cost 10 days and $20000. Managers and programmers don't understand this kind of data if they don't see ...more
A feature can be added to a well-architected software, costing 1 day and $1000. For bad architected software, the same feature cost 10 days and $20000. Managers and programmers don't understand this kind of data if they don't see ...more
This review has been hidden because it contains spoilers. To view it,
click here.
This is Robert C. Martin's book that I liked most, for a number of reasons:
1. The author discusses a number practical software design principles. The advice is often strong, but the argumentation is well thought out. It is clear that the principles are based on plenty of experience. The detail in which every principle is discussed makes this book less of a laundry list than Clean Code.
2. I thought it was quite a personal book. Contrary to some, I liked Martin's stories about his life as a softwa ...more
1. The author discusses a number practical software design principles. The advice is often strong, but the argumentation is well thought out. It is clear that the principles are based on plenty of experience. The detail in which every principle is discussed makes this book less of a laundry list than Clean Code.
2. I thought it was quite a personal book. Contrary to some, I liked Martin's stories about his life as a softwa ...more
This book was exactly what I expected it to be.
I have attended several talks by Uncle Bob and read his 'Clean Code' a long time ago. I wasn't surprised by the contents, as his stand on the architecture (as it seems to me) is consistent and stable. Some of his war stories are hard to overvalue.
The most important part I have read there is about SRP and how to understand it differently than it's commonly understood.
I recommend the book to most software engineers, to both learn, and get a topic to d ...more
I have attended several talks by Uncle Bob and read his 'Clean Code' a long time ago. I wasn't surprised by the contents, as his stand on the architecture (as it seems to me) is consistent and stable. Some of his war stories are hard to overvalue.
The most important part I have read there is about SRP and how to understand it differently than it's commonly understood.
I recommend the book to most software engineers, to both learn, and get a topic to d ...more
Uncle bob is fighting to retain the old world of software, where you architecture anything, and implement nothing. His advises may apply to old enterprises, with gigantic systems. This whole book could be summarized to twenty pages, but uncle bob is trying to make a living and earn some cash, so he his wasting your time. Would recommend reading Domain Driven Design by Eric Evans or similar books concerning DDD.
I found the book very useful and it helped me work out some of the architectural mistakes I've made in the past. It's not nearly as dense as Uncle Bob's other books (which I think is where some of the more negative reviews come from) but it does a good job of clearly laying out principles of good component design and software structures. The rest of the book gives examples of different cases where the principles apply and really Helps to bring the ideas home.
I really loved this book. It got me thinking about solving complex problems in a more systematic way, by paying attention to how sub-systems interact and putting words to how software should be built while giving practical advice for how to work on a day-to-day basis.
I would recommend this to anyone who has been programming for a while, and who works with larger code bases or with other people. For newer programmers, I'd start with his "Clean Code" book :)
I would recommend this to anyone who has been programming for a while, and who works with larger code bases or with other people. For newer programmers, I'd start with his "Clean Code" book :)
Like other reviewers, I don't think I learnt much from this book. As much as I admire and respect Uncle Bob, it feels like he's going over the same SOLID principles again, without providing any in-depth examples, just vague general advice. And it's good advice, and it's nice to be reminded... but at some point it would be great to have something concrete to discuss -common mistakes, pitfalls, why and how to avoid them, that kind of thing.
I really liked the Clean series. They describe guidelines and rules of thumb that I find useful and enjoyable to follow. With this one I noticed I knew a lot of the stuff in it, because I have read the "Agile Software Development" book, but because the main focus was on architecture, I learned new things while at the same time I refreshed old knowledge from a different angle. I recommend this one (together with Clean Code and The Clean Coder).
Nice book!
But if you already read Clean code, you will be disappointed on it. It's too much about SOLID principle, what we already read in Clean code, but only few new details related to architecture.
-never "mariage" on framework, don't allow to be framework part of business logic
- GUI only details
- Database only detail
- Don't cross layer boundaries
- Delay decision about DB or framework as much as possible
Interesting was to read appendix, some autobiography of Uncle Bob.
But if you already read Clean code, you will be disappointed on it. It's too much about SOLID principle, what we already read in Clean code, but only few new details related to architecture.
-never "mariage" on framework, don't allow to be framework part of business logic
- GUI only details
- Database only detail
- Don't cross layer boundaries
- Delay decision about DB or framework as much as possible
Interesting was to read appendix, some autobiography of Uncle Bob.
There are no discussion topics on this book yet.
Be the first to start one »
Goodreads is hiring!
Robert Cecil Martin, commonly called Uncle Bob, is a software engineer, advocate of Agile development methods, and President of Object Mentor Inc. Martin and his team of software consultants use Object-Oriented Design, Patterns, UML, Agile Methodologies, and eXtreme Programming with worldwide clients.
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio ...more
He was Editor in Chief of the C++ Report from 1996 to 1999. He is a featured speaker at internatio ...more
No trivia or quizzes yet. Add some now »
“Science does not work by proving statements true, but rather by proving statements false.”
—
1 likes
“Architecting for the enterprise, when all you really need is a cute little desktop tool, is a recipe for failure.”
—
0 likes
More quotes…
