Clean Architecture 软件架构与设计匠艺 英文版【2025|PDF|Epub|mobi|kindle电子书版本百度云盘下载】

Clean Architecture 软件架构与设计匠艺 英文版PDF格式电子书版下载

注意：本站所有压缩包均有解压码： 点击下载压缩包解压工具

PART Ⅰ Introduction1

Chapter 1 What Is Design and Architecture？3

The Goal？4

Case Study5

Conclusion12

Chapter 2 A Tale of Two Values13

Behavior14

Architecture14

The Greater Value15

Eisenhower’s Matrix16

Fight for the Architecture18

PART Ⅱ Starting with the Bricks:Programming Paradigms19

Chapter 3 Paradigm Overview21

Structured Programming22

Object-Oriented Programming22

Functional Programming22

Food for Thought23

Conclusion24

Chapter 4 Structured Programming25

Proof27

A Harmful Proclamation28

Functional Decomposition29

No Formal Proofs30

Science to the Rescue30

Tests31

Conclusion31

Chapter 5 Object-Oriented Programming33

Encapsulation？34

Inheritance？37

Polymorphism？40

Conclusion47

Chapter 6 F unctional Programming49

Squares of Integers50

Immutability and Architecture52

Segregation of Mutability52

Event Sourcing54

Conclusion56

PART Ⅲ Design Principles57

Chapter 7 SRP:The Single Responsibility Principle61

Symptom 1:Accidental Duplication63

Symptom 2:Merges65

Solutions66

Conclusion67

Chapter 8 OCP:The Open-Closed Principle69

A Thought Experiment70

Directional Control74

Information Hiding74

Conclusion75

Chapter 9 LSP:The Liskov Substitution Principle77

Guiding the Use of Inheritance78

The Square/Rectangle Problem79

LSP and Architecture80

Example LSP Violation80

Conclusion82

Chapter 10 ISP:The Interface Segregation Principle83

ISP and Language85

ISP and Architecture86

Conclusion86

Chapter 11 DIP:The Dependency Inversion Principle87

Stable Abstractions88

Factories89

Concrete Components91

Conclusion91

PART Ⅳ Component Principles93

Chapter 12 Components95

A Brief History of Components96

Relocatability99

Linkers100

Conclusion102

Chapter 13 Component Cohesion103

The Reuse/Release Equivalence Principle104

The Common Closure Principle105

The Common Reuse Principle107

The Tension Diagram for Component Cohesion108

Conclusion110

Chapter 14 Component Coupling111

The Acyclic Dependencies Principle112

Top-Down Design118

The Stable Dependencies Principle120

The Stable Abstractions Principle126

Conclusion132

PART Ⅴ Architecture133

Chapter 15 What Is Architecture？135

Development137

Deployment138

Operation138

Maintenance139

Keeping Options Open140

Device Independence142

Junk Mail144

Physical Addressing145

Conclusion146

Chapter 16 Independence147

Use Cases148

Operation149

Development149

Deployment150

Leaving Options Open150

Decoupling Layers151

Decoupling Use Cases152

Decoupling Mode153

Independent Develop-ability153

Independent Deployability154

Duplication154

Decoupling Modes（Again）155

Conclusion158

Chapter 17 Boundaries:Drawing Lines159

A Couple of Sad Stories160

FitNesse163

Which Lines Do You Draw,and When Do You Draw Them？165

What About Input and Output？169

Plugin Architecture170

The Plugin Argument172

Conclusion173

Chapter 18 Boundary Anatomy175

Boundary Crossing176

The Dreaded Monolith176

Deployment Components178

Threads179

Local Processes179

Services180

Conclusion181

Chapter 19 Policy and Level183

Level184

Conclusion187

Chapter 20 Business Rules189

Entities190

Use Cases191

Request and Response Models193

Conclusion194

Chapter 21 Screaming Architecture195

The Theme of an Architecture196

The Purpose of an Architecture197

But What About the Web？197

Frameworks Are Tools,Not Ways of Life198

Testable Architectures198

Conclusion199

Chapter 22 The Clean Architecture201

The Dependency Rule203

A Typical Scenario207

Conclusion209

Chapter 23 Presenters and Humble Objects211

The Humble Object Pattern212

Presenters and Views212

Testing and Architecture213

Database Gateways214

Data Mappers214

Service Listeners215

Conclusion215

Chapter 24 Partial Boundaries217

Skip the Last Step218

One-Dimensional Boundaries219

Facades220

Conclusion220

Chapter 25 Layers and Boundaries221

Hunt the Wumpus222

Clean Architecture？223

Crossing the Streams226

Splitting the Streams227

Conclusion228

Chapter 26 The Main Component231

The Ultimate Detail232

Conclusion237

Chapter 27 Services:Great and Small239

Service Architecture？240

Service Benefits？240

The Kitty Problem242

Objects to the Rescue244

Component-Based Services245

Cross-Cutting Concerns246

Conclusion247

Chapter 28 The Test Boundary249

Tests as System Components250

Design for Testability251

The Testing API252

Conclusion253

Chapter 29 Clean Embedded Architecture255

App-titude Test258

The Target-Hardware Bottleneck261

Conclusion273

PART Ⅵ Details275

Chapter 30 The Database Is a Detail277

Relational Databases278

Why Are Database Systems So Prevalent？279

What If There Were No Disk？280

Details281

But What about Performance？281

Anecdote281

Conclusion283

Chapter 31 The Web Is a Detail285

The Endless Pendulum286

The Upshot288

Conclusion289

Chapter 32 Frameworks Are Details291

Framework Authors292

Asymmetric Marriage292

The Risks293

The Solution294

I Now Pronounce You295

Conclusion295

Chapter 33 Case Study:Video Sales297

The Product298

Use Case Analysis298

Component Architecture300

Dependency Management302

Conclusion302

Chapter 34 The Missing Chapter303

Package by Layer304

Package by Feature306

Ports and Adapters308

Package by Component310

The Devil Is in the Implementation Details315

Organization versus Encapsulation316

Other Decoupling Modes319

Conclusion:The Missing Advice321

PART Ⅶ Appendix323

Appendix A Architecture Archaeology325

Index375