--- product_id: 46755671 title: "Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series)" price: "288 zł" currency: PLN in_stock: true reviews_count: 9 url: https://www.desertcart.pl/products/46755671-clean-architecture-a-craftsmans-guide-to-software-structure-and-design store_origin: PL region: Poland --- # Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) **Price:** 288 zł **Availability:** ✅ In Stock ## Quick Answers - **What is this?** Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) - **How much does it cost?** 288 zł with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.pl](https://www.desertcart.pl/products/46755671-clean-architecture-a-craftsmans-guide-to-software-structure-and-design) ## Best For - Customers looking for quality international products ## Why This Product - Free international shipping included - Worldwide delivery with tracking - 15-day hassle-free returns ## Description Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) [Martin, Robert] on desertcart.com. *FREE* shipping on qualifying offers. Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) Review: Good book; well written; insightful - Highly recommended for software developers who want to improve code quality! Review: Capital Work on Software Architecture By An Architecture Master - 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. ## Technical Specifications | Specification | Value | |---------------|-------| | Best Sellers Rank | #34,054 in Books ( See Top 100 in Books ) #4 in Software Design & Engineering #22 in Software Development (Books) #76 in Business Technology | | Customer Reviews | 4.6 4.6 out of 5 stars (4,009) | | Dimensions | 0.8 x 6.9 x 9 inches | | Edition | 1st | | ISBN-10 | 0134494164 | | ISBN-13 | 978-0134494166 | | Item Weight | 3.99 ounces | | Language | English | | Part of series | Robert C. Martin Series | | Print length | 432 pages | | Publication date | September 10, 2017 | | Publisher | Pearson | ## Images ![Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) - Image 1](https://m.media-amazon.com/images/I/71stxGw9JgL.jpg) ## Customer Reviews ### ⭐⭐⭐⭐⭐ Good book; well written; insightful *by E***R on April 16, 2026* Highly recommended for software developers who want to improve code quality! ### ⭐⭐⭐⭐⭐ Capital Work on Software Architecture By An Architecture Master *by C***A on August 18, 2018* 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. ### ⭐⭐⭐⭐ Some good thinking on a limited subset of application architecture *by K***S on August 16, 2019* 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. ## Frequently Bought Together - Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series) - Clean Code: A Handbook of Agile Software Craftsmanship - Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems --- ## Why Shop on Desertcart? - 🛒 **Trusted by 1.3+ Million Shoppers** — Serving international shoppers since 2016 - 🌍 **Shop Globally** — Access 737+ million products across 21 categories - 💰 **No Hidden Fees** — All customs, duties, and taxes included in the price - 🔄 **15-Day Free Returns** — Hassle-free returns (30 days for PRO members) - 🔒 **Secure Payments** — Trusted payment options with buyer protection - ⭐ **TrustPilot Rated 4.5/5** — Based on 8,000+ happy customer reviews **Shop now:** [https://www.desertcart.pl/products/46755671-clean-architecture-a-craftsmans-guide-to-software-structure-and-design](https://www.desertcart.pl/products/46755671-clean-architecture-a-craftsmans-guide-to-software-structure-and-design) --- *Product available on Desertcart Poland* *Store origin: PL* *Last updated: 2026-04-29*