
Clean Architecture
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin ("Uncle Bob") reveals those rules and helps you apply them.
Martin's Clean Architecture doesn't merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you've come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you'll face-the ones that will make or break your projects.
Learn what software architects need to achieve-and core disciplines and practices for achieving it
Master essential software design principles for addressing function, component separation, and data management
See how programming paradigms impose discipline by restricting what developers can do
Understand what's critically important and what's merely a "detail"
Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications
Define appropriate boundaries and layers, and organize components and services
See why designs and architectures go wrong, and how to prevent (or fix) these failures
Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager-and for every programmer who must execute someone else's designs.
Register your product for convenient access to downloads, updates, and/or corrections as they become available.
More details
Other editions
Additional editions

Person
Content
Chapter 2: A Tale of Two Values
Chapter 3: Paradigm Overview
Chapter 4: Structured Programming
Chapter 5: Object-Oriented Programming
Chapter 6: Functional Programming
Chapter 7: SRP: The Single Responsibility Principle
Chapter 8: OCP: The Open-Closed Principle
Chapter 9: LSP: The Liskov Substitution Principle
Chapter 10: ISP: The Interface Segregation Principle
Chapter 11: DIP: The Dependency Inversion Principle 8
Chapter 12: Components
Chapter 13: Component Cohesion
Chapter 14: Component Coupling
Chapter 15: What Is Architecture?
Chapter 16: Independence
Chapter 17: Boundaries: Drawing Lines
Chapter 18: Boundary Anatomy
Chapter 19: Policy and Level
Chapter 20: Business Rules
Chapter 21: Screaming Architecture
Chapter 22: The Clean Architecture
Chapter 23: Presenters and Humble Objects
Chapter 24: Partial Boundaries
Chapter 25: Layers and Boundaries
Chapter 26: The Main Component
Chapter 27: Services: Great and Small
Chapter 28: The Test Boundary
Chapter 29: Clean Embedded Architecture
Chapter 30: The Database Is a Detail
Chapter 31: The Web Is a Detail
Chapter 32: Frameworks Are Details
Chapter 33: Case Study: Video Sales
Chapter 34: The Missing Chapter
System requirements
File format: ePUB
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use a reading software that can process the file format ePUB: e.g., Adobe Digital Editions or FBReader – both free (see eBook Help).
- Tablet/Smartphone (Android; iOS): Before downloading, install the free app Adobe Digital Editions (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePUB works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.