50 principles for highly scalable websites

50 principles for highly scalable websites
Basic Information
Original Title: scalability rules: 50 principles for scaling Web Sites
Author: (US) Martin L. Abbott Michael T. Fisher
Translator: Zhang Xin Yang hailing
Series name: Turing programming Series
Press: People's post and telecommunications Press
ISBN: 9787115275721
Mounting time:
Published on: February 1, June 2012
Start: 16
Page number: 1
Version: 1-1
Category: Computer> Computer Network> Web Server
> Comprehensive

More details, 50 high-scalability website principles
Introduction
Computer books
Reducing DNS in the 50 principles for highly scalable websites
Search, minimize objects, and so on. Each principle is bound to a different topic. Most of the Principles are technology-oriented. Only a few principles solve problems related to key habits and Methods. Of course, each principle is crucial to building scalable products.

The 50 principles for highly scalable websites are suitable for Web developers at all levels.
Go back to the top of the "50 principles for highly scalable websites"
Chapter 1 simplification equation 1
1.1 Principle 1: Do not overdesign 2
1.2 Principle 2: design considerations for scalability (d-I-d method) 6
1.2.1 Design 7
1.2.2 implementation 8
1.2.3 deployment 8
1.3 Principle 3: simplify the solution 10
1.3.1 how to simplify range 10
1.3.2 how to simplify design 11
1.3.3 how to simplify implementation 12
1.4 Principle 4: Reduce DNS lookup 13
1.5 Principle 5: Minimize objects by 16
1.6 Principle 6: Use network devices of the same brand 19
1.7 Conclusion 21
References 21
Chapter 2 Distribution 23
2.1 Principle 7: horizontal replication (X axis principle) 25
2.2 Principle 8: splitting different things (Y axis principle) 29
2.3 Principle 9: splitting similar things (Z axis principle) 32

. 2.4 Summary 34
Reference 34
Chapter 1 horizontal scaling design 35
3.1 Principle 10: Design of horizontal scaling solution 36
3.2 Principle 11: economic system 39
3.3 Principle 12: horizontal expansion of data centers 42
3.4 Principle 13: Design Using Cloud technology 48
3.5 summary 50
References 50
Chapter 5 use the correct tool 51
4.1 principle 14: rational use of the database 52
4.2 Principle 15: firewalls are everywhere 59
4.3 Principle 16: active use of log files 63
4.4 summary 66
References 66
Chapter 1 do not repeat 67
5.1 Principle 17: do not immediately check the work you have just done 68
5.2 Principle 18: Stop redirection 72
5.3 Principle 19: relaxation timing constraints 77
5.4 Summary 80
References 80
Chapter 1 active use of cache 81
6.1 Principle 20: Using CDN 82
6.2 Principle 21: Use the expired header 85
6.3 Principle 22: cache Ajax call 90
6.4 principle 23: using page cache 95
6.5 Principle 24: Using application cache 98
6.6 Principle 25: Use object cache 102
6.7 principle 26: Put the object cache on its own "layer" 105
6.8 conclusion 107
References 107
Chapter 4 lessons learned from errors 7th
7.1 Principle 27: actively learn 110
7.2 Principle 28: do not rely on QA to discover 113 errors
7.3 Principle 29: design without rollback is a failed design 117
7.4 Principle 30: Failure in discussion and Lessons Learned 120
7.5 conclusion 124
References 124
Chapter 2 database principles 8th
8.1 principle 31: Pay attention to the high-cost relationship 126
8.2 Principle 32: Use a database lock of the correct Type 130
8.3 Principle 33: Do not use multi-stage commit 133
8.4 principle 34: Do not use select for update 135
8.5 principle 35: do not select all data 137
8.6 conclusion 140
References 140
Chapter 2 Fault Tolerance Design and fault control 9th
9.1 Principle 36: Adopt fault isolation "Lane" 142
9.2 Principle 37: Never trust spof 148
9.3 Principle 38: Avoid system connection 151
9.4 principle 39: ensure that the feature is enabled/disabled 155
9.5 conclusion 158
Chapter 1 avoidance or distribution status 10th
10.1 principle 40: strive to achieve stateless 161
10.2 principle 41: maintain sessions on the browser as much as possible 164
10.3 Principle 42: using distributed cache to store status 167
10.4 Conclusion 170
References 170
Chapter 2 asynchronous communication and message bus 11th
11.1 principle 43: use Asynchronous Communication as much as possible 172
11.2 principle 44: ensure that the message bus can be expanded by 175
11.3 Principle 45: avoid over-crowded message bus by 179
11.4 conclusion 182
Chapter 2 other principles 12th
12.1 principle 46: Use third-party solutions with caution to expand 184
12.2 principle 47: clean, archive and 187 of the cost of storage
12.3 principle 48: delete Business Intelligence in transaction processing 192
12.4 Principle 49: Design of applications that can be monitored 195
12.5 principle 50: competent 199
12.6 Conclusion 202
References 202
Chapter 1 principle review and priority assignment 13th
13.1 assess the risks of expansion projects and initiative? Revenue model 204
13.2 benefit/Priority Level of expansion principle 235
13.3 conclusion 238

Source of this book: China Interactive publishing network