Clean Architecture:軟件架構與設計匠藝(英文版)

Clean Architecture:軟件架構與設計匠藝(英文版) pdf epub mobi txt 電子書 下載2025

出版者:電子工業齣版社
作者:【美】Robert C. Martin(羅伯特·C·馬丁)
出品人:
頁數:424
译者:
出版時間:2018-7
價格:109.00元
裝幀:平裝
isbn號碼:9787121342615
叢書系列:原味精品書係
圖書標籤:
  • 架構
  • 軟件架構
  • 軟件設計
  • architecture
  • 計算機
  • 編程
  • 軟件工程/設計模式/架構
  • 美國
  • 軟件架構
  • 設計模式
  • 整潔架構
  • 代碼質量
  • 可維護性
  • 可測試性
  • 領域驅動設計
  • 軟件工程
  • Robert C
  • Martin
  • Clean Code
想要找書就要到 小美書屋
立刻按 ctrl+D收藏本頁
你會得到大驚喜!!

具體描述

通過閤理運用軟件架構的通用法則,可以顯著提升開發者在所有軟件係統全生命周期內的生産力。如今,傳奇軟件匠師Robert C. Martin(Bob 大叔),攜暢銷書Clean Code 與The CleanCoder 所獲巨大成功之威,深刻揭示這些法則並親授運用之道。Martin 在《Clean Architecture:軟件架構與設計匠藝(英文版)》中遠不隻是在為我們提供選項,他幾乎是在將軟件世界中橫跨半個世紀的各種架構類型的設計經驗傾囊相授,目的是讓讀者既能閱盡所有架構選型,又可通曉其如何決定成敗。Bob 大叔也的確不負厚望,《Clean Architecture:軟件架構與設計匠藝(英文版)》中充滿瞭直接而有效的解決方案,以供讀者應對所麵臨的真正挑戰——那些或最終成就或徹底破壞你項目的挑戰。

著者簡介

Robert C. Martin(Bob大叔)從1970年編程至今。他是cleancoders.com的聯閤創始人,該網站為軟件開發者提供在綫視頻教育。同時,他還是Bob大叔谘詢公司的創始人,該公司為全球大型公司提供軟件開發谘詢服務、培訓以及技能培訓服務。同時,他在 8th Light公司任“首席匠人”一職,該公司是位於芝加哥的一傢軟件開發谘詢公司。本書作者在各種行業周刊上發錶瞭十餘篇文章,同時也經常被國際會議和行業峰會邀請進行演講。他曾任C++ Report的主編,並且曾任敏捷聯盟(Agile Aliance)的主席。

Martin曾經編寫和參與編輯瞭多本圖書,包括The Clean Coder、Clean Code、UML for Java Programmers、Agile Software Development、Extreme Programming in Practice、More C++ Gems、Pattern Languages of Program Design 3,以及Designing Object Oriented C++ Applications Using the Booch Method。

圖書目錄

PART I Introduction 1
Chapter 1 What Is Design and Architecture? 3
The Goal? 4
Case Study 5
Conclusion 12
Chapter 2 A Tale of Two Values 13
Behavior 14
Architecture 14
The Greater Value 15
Eisenhower’s Matrix 16
Fight for the Architecture 18
PART II Starting with the Bricks: Programming Paradigms 19
Chapter 3 Paradigm Overview 21
Structured Programming 22
Object-Oriented Programming 22
Functional Programming 22
Food for Thought 23
Conclusion 24
Chapter 4 Structured Programming 25
Proof 27
A Harmful Proclamation 28
Functional Decomposition 29
No Formal Proofs 30
Science to the Rescue 30
Tests 31
Conclusion 31
Chapter 5 Object-Oriented Programming 33
Encapsulation? 34
Inheritance? 37
Polymorphism? 40
Conclusion 47
Chapter 6 Functional Programming 49
Squares of Integers 50
Immutability and Architecture 52
Segregation of Mutability 52
Event Sourcing 54
Conclusion 56
PART III Design Principles 57
Chapter 7 SRP: The Single Responsibility Principle 61
Symptom 1: Accidental Duplication 63
Symptom 2: Merges 65
Solutions 66
Conclusion 67
Chapter 8 OCP: The Open-Closed Principle 69
A Thought Experiment 70
Directional Control 74
Information Hiding 74
Conclusion 75
Chapter 9 LSP: The Liskov Substitution Principle 77
Guiding the Use of Inheritance 78
The Square/Rectangle Problem 79
LSP and Architecture 80
Example LSP Violation 80
Conclusion 82
Chapter 10 ISP: The Interface Segregation Principle 83
ISP and Language 85
ISP and Architecture 86
Conclusion 86
Chapter 11 DIP: The Dependency Inversion Principle 87
Stable Abstractions 88
Factories 89
Concrete Components 91
Conclusion 91
PART IV Component Principles 93
Chapter 12 Components 95
A Brief History of Components 96
Relocatability 99
Linkers 100
Conclusion 102
Chapter 13 Component Cohesion 103
The Reuse/Release Equivalence Principle 104
The Common Closure Principle 105
The Common Reuse Principle 107
The Tension Diagram for Component Cohesion 108
Conclusion 110
Chapter 14 Component Coupling 111
The Acyclic Dependencies Principle 112
Top-Down Design 118
The Stable Dependencies Principle 120
The Stable Abstractions Principle 126
Conclusion 132
PART V Architecture 133
Chapter 15 What Is Architecture? 135
Development 137
Deployment 138
Operation 138
Maintenance 139
Keeping Options Open 140
Device Independence 142
Junk Mail 144
Physical Addressing 145
Conclusion 146
Chapter 16 Independence 147
Use Cases 148
Operation 149
Development 149
Deployment 150
Leaving Options Open 150
Decoupling Layers 151
Decoupling Use Cases 152
Decoupling Mode 153
Independent Develop-ability 153
Independent Deployability 154
Duplication 154
Decoupling Modes (Again) 155
Conclusion 158
Chapter 17 Boundaries: Drawing Lines 159
A Couple of Sad Stories 160
FitNesse 163
Which Lines Do You Draw, and When Do You Draw Them? 165
What About Input and Output? 169
Plugin Architecture 170
The Plugin Argument 172
Conclusion 173
Chapter 18 Boundary Anatomy 175
Boundary Crossing 176
The Dreaded Monolith 176
Deployment Components 178
Threads 179
Local Processes 179
Services 180
Conclusion 181
Chapter 19 Policy and Level 183
Level 184
Conclusion 187
Chapter 20 Business Rules 189
Entities 190
Use Cases 191
Request and Response Models 193
Conclusion 194
Chapter 21 Screaming Architecture 195
The Theme of an Architecture 196
The Purpose of an Architecture 197
But What About the Web? 197
Frameworks Are Tools, Not Ways of Life 198
Testable Architectures 198
Conclusion 199
Chapter 22 The Clean Architecture 201
The Dependency Rule 203
A Typical Scenario 207
Conclusion 209
Chapter 23 Presenters and Humble Objects 211
The Humble Object Pattern 212
Presenters and Views 212
Testing and Architecture 213
Database Gateways 214
Data Mappers 214
Service Listeners 215
Conclusion 215
Chapter 24 Partial Boundaries 217
Skip the Last Step 218
One-Dimensional Boundaries 219
Facades 220
Conclusion 220
Chapter 25 Layers and Boundaries 221
Hunt the Wumpus 222
Clean Architecture? 223
Crossing the Streams 226
Splitting the Streams 227
Conclusion 228
Chapter 26 The Main Component 231
The Ultimate Detail 232
Conclusion 237
Chapter 27 Services: Great and Small 239
Service Architecture? 240
Service Benefits? 240
The Kitty Problem 242
Objects to the Rescue 244
Component-Based Services 245
Cross-Cutting Concerns 246
Conclusion 247
Chapter 28 The Test Boundary 249
Tests as System Components 250
Design for Testability 251
The Testing API 252
Conclusion 253
Chapter 29 Clean Embedded Architecture 255
App-titude Test 258
The Target-Hardware Bottleneck 261
Conclusion 273
PART VI Details 275
Chapter 30 The Database Is a Detail 277
Relational Databases 278
Why Are Database Systems So Prevalent? 279
What If There Were No Disk? 280
Details 281
But What about Performance? 281
Anecdote 281
Conclusion 283
Chapter 31 The Web Is a Detail 285
The Endless Pendulum 286
The Upshot 288
Conclusion 289
Chapter 32 Frameworks Are Details 291
Framework Authors 292
Asymmetric Marriage 292
The Risks 293
The Solution 294
I Now Pronounce You … 295
Conclusion 295
Chapter 33 Case Study: Video Sales 297
The Product 298
Use Case Analysis 298
Component Architecture 300
Dependency Management 302
Conclusion 302
Chapter 34 The Missing Chapter 303
Package by Layer 304
Package by Feature 306
Ports and Adapters 308
Package by Component 310
The Devil Is in the Implementation Details 315
Organization versus Encapsulation 316
Other Decoupling Modes 319
Conclusion: The Missing Advice 321
PART VII Appendix 323
Appendix A Architecture Archaeology 325
Index 375
· · · · · · (收起)

讀後感

評分

評分

最初在网店发现这本书时,一看到书名我就很开心:Uncle Bob 出新书啦。扫了一眼目录,又心生疑惑:全书分为6个部分,第3个部分才讲到 SOLID 原则。这些原则在他的巨著《敏捷软件开发:原则、模式与实践》里已经花大量篇幅讲解了。莫不成连 Uncle Bob 也炒起冷饭了? (没错,上...  

評分

重提了一遍各种principles。SOLID中S和D的思想贯穿整本书。收获最大的还是D,Dependecy Invsrsion。通过interface(或者说Polymorphism),使得在boundary crossing的时候,“底层”指向“高层”。感觉是从另外一个角度去看待interface如何解耦合。  

評分

uncle bob作为有50年开发经验的程序员,以下1,2,4观点可用于回答一些常见的问题。3对常见编程范式的总结很精辟 1,设计design和架构architecture没有区别,底层设计细节和高层架构信息是不可分割的,他们组合在一起,共同定义了整个软件系统 2,行为价值和架构价值,架构价值...

評分

这是一本讲架构设计之道的书; 道理,说简单也简单,就是根据功能的层次和依赖关系解耦合;说复杂也复杂,如何在架构理想和项目现实之间平衡,不是书本可以说清楚学得到的。知易行难是永远难以解决的问题。 作为一个同在PDP11上写出Hello world的老工程师,我对Martin老师所述...  

用戶評價

评分

SOLID + Component + Dependency Rule + Dependency Rule 核心觀點和敏捷裏的一緻。作為隻寫業務的人來說,很熟悉,但是對於架構這個詞來說一直朦朦朧朧,看完Bob的書以為明白瞭,仔細迴味依然在雲中。

评分

核心觀點之前已經在《敏捷軟件開發》和博客裏寫瞭,但依然是目前為止我看到最係統的講架構的書,還得好好咀嚼一下。 冷靜下來想想,還是說的略顯囉嗦,主要還是大部分觀點不是新觀點瞭。

评分

寫的很好很清晰,看得齣作者對這個領域有完整的認識。

评分

核心觀點之前已經在《敏捷軟件開發》和博客裏寫瞭,但依然是目前為止我看到最係統的講架構的書,還得好好咀嚼一下。 冷靜下來想想,還是說的略顯囉嗦,主要還是大部分觀點不是新觀點瞭。

评分

核心觀點之前已經在《敏捷軟件開發》和博客裏寫瞭,但依然是目前為止我看到最係統的講架構的書,還得好好咀嚼一下。 冷靜下來想想,還是說的略顯囉嗦,主要還是大部分觀點不是新觀點瞭。

本站所有內容均為互聯網搜索引擎提供的公開搜索信息,本站不存儲任何數據與內容,任何內容與數據均與本站無關,如有需要請聯繫相關搜索引擎包括但不限於百度google,bing,sogou

© 2025 book.quotespace.org All Rights Reserved. 小美書屋 版权所有