Clean Architecture: A Craftsman's Guide to Software Structure and 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 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 !!!!

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

No doubt that Robert C. Martin is one of the most influential author and software development theorist of our times. The already standard SOLID principles had been with us for decades, serving software discipline with full success. The Clean Series is a set of books full of advises, thoughts, ideas, rationales and principles with the same impact. If you know his videos and lectures, probably this book will see familiar and many of the topics discussed repetitive. But the book has the value to reunite and review his software development discipline philosophy in a concise and complete harmonious set of essays. The main idea is to avoid dependency applying the Dependency Rule at all levels, classes and components. The Dependency Inversion graph, where high-level functions calling middle-level functions through an interface that the middle-interface implements, is a medular software construction that should be applied as an obsessive pattern. It guarantees independence, reusable, clean architecture. This book explains how and why for this. The result is the idea of Plugin architecture where the core of the system, the set of functionality that implements the use cases and business rules (interactors (R. C. Martin)/controls (I. Jacobson)/controllers (C. Larman) should be the center at which all other parts (IO components, details) will point via abstractions (interfaces or abstract classes). I have been practicing clean architecture ideas for many years (and before Martin coined the term) following Martin guidance a principles. Its product is natural, simple, robust, structured, reusable and beautiful to work. Paradoxically, the last chapter about packaging components--written by S. Brown--seems a contradiction to the whole book ideas and Brown somehow point to that ("My definition of a component is slightly different..."). In that chapter, Brown explains several alternatives for software architecture organization with a marked inclination for a monolithic package that represents the services of the system (and repository interaction) and another that represents the controllers. The reasons of that resultant recommendation (a junior undisciplined programmer that don't follow the cleanliness of the architecture, etc.) are really weak and out of the architect control. His recommendation violates almost all components principles explained by Martin (REP, CCP, CRP, etc.) I love this book and totally recommend the book for all fans of good, clean architecture.

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

The book itself, a must have. I was disappointed to receive a used copy. I requested to replace it considering the price, but nothing happened.

Dobra zawartość, dobrze się czyta. Nic tylko polecać chcącym poszerzać swoją wiedzę.

This book is a real gem in the software architecture field. It discusses the basics and programming paradigms, then goes up a level and speaks about component cohesion, then component coupling, sketches up a general architecture model that relies on these principles, and then explains many different cases and patterns. Arguably one of the most valuable books I've ever read.

Martin follows a clean and practical approach in this book. He explains with great pedagogy key concept of the architecture. As any other book of practices, this is a merely guide or tool, so you should be careful and diligent evaluating your requirements to see if the advice given in the book applies to you.

A must-read if you care about the architecture of the software you are working on. You don't have to follow all the rules by the book, but the reflection about architecture is what matters.