Clean Architecture: A Guide to Software Design

I have read four books, dozens of articles, and have watched scores of videos by Uncle Bob. As always I found this one fascinating and well written. Bob has a flare for synthesizing very complex technical material from many sources, then boiling it down to easily and enjoyably absorbable explanations. He manages the magic of combining theoretically deep discussion with a very practical, even advice-like perspective. I'm so happy he's made himself the uncle of young programmers like me and invited us to squat on his lawn. My caveat is that, having gone through so much of Bob's previous material, there was unfortunately much here that was already familiar to me, including some sections that are taken almost verbatim from his previous writings. In itself this is no problem - had it been the first I ever read of the man I would be totally ecstatic about it, and it's reasonable of him to assume that most readers would not have followed him around the internets as assiduously as I have. But I was hoping to hear more about topics he only hinted at in his blog posts, e.g. the different kinds of architecture implied by different desired user experiences. I read him mention event-driven, request-based, and batch processing, and I was assuming he would elaborate on these ideas in this book, which he does not. There are many other details I wish he'd gone into or at least offered good follow-up reading on, such as presenters and the creation of use cases. Finally, he does not appear to provide the name of the stellar body on the cover, which is an unfortunate break with custom.

This book provides outstanding insight into good, clean software architecture. It should be mandatory reading for software engineering students!!

I found a lot of the explanations to be very clear and thought provoking. However, there is little practical advice on making trade-offs, supporting operational requirements, etc. This is a book about structuring software components. The subtitle says as much, so you shouldn't expect a complete guide on application, system or enterprise architecture. In fact the author seems to misunderstand the meaning of "service architecture". I think, overall, this is a very limited, if important, perspective on software architecture. Still, it's a relatively light read with interesting insights.

From Robert c Martin you can expect quality every time

This book is pure history, really enjoyable reading, the autor experience is priceless and the examples in every chapter gives you how the engineers work back in the day !!!!