book

Clean Architecture: A Craftsman's Guide to Software Structure and Design

Name: Clean Architecture: A Craftsman's Guide to Software Structure and Design
Author: Robert C. Martin
ISBN: 9780134494272

by Robert C. Martin

September 2017

Intermediate to advanced

432 pages

8h 20m

English

Pearson

Read now

Unlock full access

Includes

Sandbox

Cover Page
Series Page
Title Page
Copyright Page
Dedication
Contents
Foreword
Preface
Acknowledgments
About the Author

PART I Introduction
Chapter 1 What Is Design and Architecture?
The Goal?Case StudyConclusion
Chapter 2 A Tale of Two Values
BehaviorArchitectureThe Greater ValueEisenhower’s MatrixFight for the Architecture
PART II Starting with the Bricks: Programming Paradigms
Chapter 3 Paradigm Overview
Structured ProgrammingObject-Oriented ProgrammingFunctional ProgrammingFood for ThoughtConclusion
Chapter 4 Structured Programming
ProofA Harmful ProclamationFunctional DecompositionNo Formal ProofsScience to the RescueTestsConclusion
Chapter 5 Object-Oriented Programming
Encapsulation?Inheritance?Polymorphism?Conclusion
Chapter 6 Functional Programming
Squares of IntegersImmutability and ArchitectureSegregation of MutabilityEvent SourcingConclusion
PART III Design Principles
Chapter 7 SRP: The Single Responsibility Principle
Symptom 1: Accidental DuplicationSymptom 2: MergesSolutionsConclusion
Chapter 8 OCP: The Open-Closed Principle
A Thought ExperimentDirectional ControlInformation HidingConclusion
Chapter 9 LSP: The Liskov Substitution Principle
Guiding the Use of InheritanceThe Square/Rectangle ProblemLSP and ArchitectureExample LSP ViolationConclusion
Chapter 10 ISP: The Interface Segregation Principle
ISP and LanguageISP and ArchitectureConclusion
Chapter 11 DIP: The Dependency Inversion Principle
Stable AbstractionsFactoriesConcrete ComponentsConclusion
PART IV Component Principles
Chapter 12 Components
A Brief History of ComponentsRelocatabilityLinkersConclusion
Chapter 13 Component Cohesion
The Reuse/Release Equivalence PrincipleThe Common Closure PrincipleThe Common Reuse PrincipleThe Tension Diagram for Component CohesionConclusion
Chapter 14 Component Coupling
The Acyclic Dependencies PrincipleTop-Down DesignThe Stable Dependencies PrincipleThe Stable Abstractions PrincipleConclusion
PART V Architecture
Chapter 15 What Is Architecture?
DevelopmentDeploymentOperationMaintenanceKeeping Options OpenDevice IndependenceJunk MailPhysical AddressingConclusion
Chapter 16 Independence
Use CasesOperationDevelopmentDeploymentLeaving Options OpenDecoupling LayersDecoupling Use CasesDecoupling ModeIndependent Develop-abilityIndependent DeployabilityDuplicationDecoupling Modes (Again)Conclusion
Chapter 17 Boundaries: Drawing Lines
A Couple of Sad StoriesFitNesseWhich Lines Do You Draw, and When Do You Draw Them?What About Input and Output?Plugin ArchitectureThe Plugin ArgumentConclusion
Chapter 18 Boundary Anatomy
Boundary CrossingThe Dreaded MonolithDeployment ComponentsThreadsLocal ProcessesServicesConclusion
Chapter 19 Policy and Level
LevelConclusion
Chapter 20 Business Rules
EntitiesUse CasesRequest and Response ModelsConclusion
Chapter 21 Screaming Architecture
The Theme of an ArchitectureThe Purpose of an ArchitectureBut What About the Web?Frameworks Are Tools, Not Ways of LifeTestable ArchitecturesConclusion
Chapter 22 The Clean Architecture
The Dependency RuleA Typical ScenarioConclusion
Chapter 23 Presenters and Humble Objects
The Humble Object PatternPresenters and ViewsTesting and ArchitectureDatabase GatewaysData MappersService ListenersConclusion
Chapter 24 Partial Boundaries
Skip the Last StepOne-Dimensional BoundariesFacadesConclusion
Chapter 25 Layers and Boundaries
Hunt the WumpusClean Architecture?Crossing the StreamsSplitting the StreamsConclusion
Chapter 26 The Main Component
The Ultimate DetailConclusion
Chapter 27 Services: Great and Small
Service Architecture?Service Benefits?The Kitty ProblemObjects to the RescueComponent-Based ServicesCross-Cutting ConcernsConclusion
Chapter 28 The Test Boundary
Tests as System ComponentsDesign for TestabilityThe Testing APIConclusion
Chapter 29 Clean Embedded Architecture
App-titude TestThe Target-Hardware BottleneckConclusion
PART VI Details
Chapter 30 The Database Is a Detail
Relational DatabasesWhy Are Database Systems So Prevalent?What If There Were No Disk?DetailsBut What about Performance?AnecdoteConclusion
Chapter 31 The Web Is a Detail
The Endless PendulumThe UpshotConclusion
Chapter 32 Frameworks Are Details
Framework AuthorsAsymmetric MarriageThe RisksThe SolutionI Now Pronounce You …Conclusion
Chapter 33 Case Study: Video Sales
The ProductUse Case AnalysisComponent ArchitectureDependency ManagementConclusion
Chapter 34 The Missing Chapter
Package by LayerPackage by FeaturePorts and AdaptersPackage by ComponentThe Devil Is in the Implementation DetailsOrganization versus EncapsulationOther Decoupling ModesConclusion: The Missing Advice
Afterword
PART VII Appendix
Appendix A Architecture Archaeology
Index

404

Not Found

Either this content does not exist or you do not have access to it. Try searching for something new.

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Clean Architecture: A Craftsman's Guide to Software Structure and Design

by Robert C. Martin

404

Not Found