- ホーム
- > 洋書
- > 英文書
- > Internet / Web Programming
Full Description
Fully updated! Fifty Powerful, Easy-to-Use Rules for Supporting Hyper Growth"Whether you're taking on a role as a technology leader in a new company or you simply want to make great technology decisions, Scalability Rules will be the go-to resource on your bookshelf."-Chad Dickerson, CTO, Etsy Scalability Rules, Second Edition, is the easy-to-use scalability primer and reference for every architect, developer, network/software engineer, web professional, and manager. Authors Martin L. Abbott and Michael T. Fisher have helped scale hundreds of high-growth companies and thousands of systems. Drawing on their immense experience, they present 50 up-to-the-minute technical best practices for supporting hyper growth practically anywhere. Fully updated to reflect new technical trends and experiences, this edition is even easier to read, understand, and apply. Abbott and Fisher have also added powerful "stories behind the rules": actual experiences and case studies from CTOs and technology executives at Etsy, NASDAQ, Salesforce, Shutterfly, Chegg, Warby Parker, Twitter, and other scalability pioneers.Architects will find powerful technology-agnostic insights for creating and evaluating designs. Developers will discover specific techniques for handling everything from databases to state. Managers will get invaluable help in setting goals, making decisions, and interacting with technical teams. Whatever your role, you'll find practical risk/benefit guidance for setting priorities, translating plans into action, and gaining maximum scalability at minimum cost.You'll learn how toSimplify architectures and avoid "over-engineering"Design scale into your solution, so you can scale on a just-in-time basisMake the most of cloning and replicationSeparate functionality and split data setsScale out, not upGet more out of databases without compromising scalabilityEliminate unnecessary redirects and redundant double-checkingUse caches and CDNs more aggressively, without unacceptable complexityDesign for fault tolerance, graceful failure, and easy rollbackEmphasize statelessness, and efficiently handle state when you mustEffectively utilize asynchronous communicationLearn from your own mistakes and others' high-profile failuresPrioritize your actions to get the biggest "bang for the buck"
Contents
Preface xvAcknowledgments xxiAbout the Authors xxiiiChapter 1: Reduce the Equation 1Rule 1-Don't Overengineer the Solution 3Rule 2-Design Scale into the Solution (D-I-D Process) 6Rule 3-Simplify the Solution Three Times Over 8Rule 4-Reduce DNS Lookups 10Rule 5-Reduce Objects Where Possible 12Rule 6-Use Homogeneous Networks 15Summary 15Notes 16Chapter 2: Distribute Your Work 19Rule 7-Design to Clone or Replicate Things (X Axis) 22Rule 8-Design to Split Different Things (Y Axis) 24Rule 9-Design to Split Similar Things (Z Axis) 26Summary 28Notes 28Chapter 3: Design to Scale Out Horizontally 29Rule 10-Design Your Solution to Scale Out, Not Just Up 31Rule 11-Use Commodity Systems (Goldfish Not Thoroughbreds) 33Rule 12-Scale Out Your Hosting Solution 35Rule 13-Design to Leverage the Cloud 40Summary 42Notes 42Chapter 4: Use the Right Tools 43Rule 14-Use Databases Appropriately 47Rule 15-Firewalls, Firewalls Everywhere! 52Rule 16-Actively Use Log Files 55Summary 58Notes 58Chapter 5: Get Out of Your Own Way 59Rule 17-Don't Check Your Work 61Rule 18-Stop Redirecting Traffic 64Rule 19-Relax Temporal Constraints 68Summary 70Notes 70Chapter 6: Use Caching Aggressively 73Rule 20-Leverage Content Delivery Networks 75Rule 21-Use Expires Headers 77Rule 22-Cache Ajax Calls 80Rule 23-Leverage Page Caches 84Rule 24-Utilize Application Caches 86Rule 25-Make Use of Object Caches 88Rule 26-Put Object Caches on Their Own "Tier" 90Summary 91Notes 92Chapter 7: Learn from Your Mistakes 93Rule 27-Learn Aggressively 95Rule 28-Don't Rely on QA to Find Mistakes 100Rule 29-Failing to Design for Rollback Is Designing for Failure 102Summary 105Notes 106Chapter 8: Database Rules 107Rule 30-Remove Business Intelligence from Transaction Processing 109Rule 31-Be Aware of Costly Relationships 111Rule 32-Use the Right Type of Database Lock 114Rule 33-Pass on Using Multiphase Commits 116Rule 34-Try Not to Use Select for Update 118Rule 35-Don't Select Everything 120Summary 121Notes 122Chapter 9: Design for Fault Tolerance and Graceful Failure 123Rule 36-Design Using Fault-Isolative "Swim Lanes" 124Rule 37-Never Trust Single Points of Failure 130Rule 38-Avoid Putting Systems in Series 132Rule 39-Ensure That You Can Wire On and Off Features 135Summary 138Chapter 10: Avoid or Distribute State 139Rule 40-Strive for Statelessness 140Rule 41-Maintain Sessions in the Browser When Possible 142Rule 42-Make Use of a Distributed Cache for States 144Summary 146Notes 146Chapter 11: Asynchronous Communication and Message Buses 147Rule 43-Communicate Asynchronously as Much as Possible 149Rule 44-Ensure That Your Message Bus Can Scale 151Rule 45-Avoid Overcrowding Your Message Bus 154Summary 157Chapter 12: Miscellaneous Rules 159Rule 46-Be Wary of Scaling through Third Parties 161Rule 47-Purge, Archive, and Cost-Justify Storage 163Rule 48-Partition Inductive, Deductive, Batch, and User Interaction (OLTP) Workloads 166Rule 49-Design Your Application to Be Monitored 169Rule 50-Be Competent 172Summary 174Notes 174Chapter 13: Rule Review and Prioritization 177A Risk-Benefit Model for Evaluating Scalability Projects and Initiatives 17750 Scalability Rules in Brief 180A Benefit/Priority Ranking of the Scalability Rules 200Summary 202Index 205
