Web Operations

Dedication; Foreword; Preface; How This Book Is Organized; Who This Book Is For; Conventions Used in This Book; Using Code Examples; How to Contact Us; Safari?? Books Online; Acknowledgments; Chapter 1: Web Operations: The Career; 1.1 Why Does Web Operations Have It Tough?; 1.2 From Apprentice to Master; 1.3 Conclusion; Chapter 2: How Picnik Uses Cloud Computing: Lessons Learned; 2.1 Where the Cloud Fits (and Why!); 2.2 Where the Cloud Doesn't Fit (for Picnik); 2.3 Conclusion; Chapter 3: Infrastructure and Application Metrics; 3.1 Time Resolution and Retention Concerns; 3.2 Locality of Metrics Collection and Storage; 3.3 Layers of Metrics; 3.4 Providing Context for Anomaly Detection and Alerts; 3.5 Log Lines Are Metrics, Too; 3.6 Correlation with Change Management and Incident Timelines; 3.7 Making Metrics Available to Your Alerting Mechanisms; 3.8 Using Metrics to Guide Load-Feedback Mechanisms; 3.9 A Metrics Collection System, Illustrated: Ganglia; 3.10 Conclusion; Chapter 4: Continuous Deployment; 4.1 Small Batches Mean Faster Feedback; 4.2 Small Batches Mean Problems Are Instantly Localized; 4.3 Small Batches Reduce Risk; 4.4 Small Batches Reduce Overhead; 4.5 The Quality Defenders' Lament; 4.6 Getting Started; 4.7 Continuous Deployment Is for Mission-Critical Applications; 4.8 Conclusion; Chapter 5: Infrastructure As Code; 5.1 Service-Oriented Architecture; 5.2 Conclusion; Chapter 6: Monitoring; 6.1 Story: "The Start of a Journey"; 6.2 Step 1: Understand What You Are Monitoring; 6.3 Step 2: Understand Normal Behavior; 6.4 Step 3: Be Prepared and Learn; 6.5 Conclusion; Chapter 7: How Complex Systems Fail; 7.1 How Complex Systems Fail; 7.2 Further Reading; Chapter 8: Community Management and Web Operations; Chapter 9: Dealing with Unexpected Traffic Spikes; 9.1 How It All Started; 9.2 Alarms Abound; 9.3 Putting Out the Fire; 9.4 Surviving the Weekend; 9.5 Preparing for the Future; 9.6 CDN to the Rescue; 9.7 Proxy Servers; 9.8 Corralling the Stampede; 9.9 Streamlining the Codebase; 9.10 How Do We Know It Works?; 9.11 The Real Test; 9.12 Lessons Learned; 9.13 Improvements Since Then; Chapter 10: Dev and Ops Collaboration and Cooperation; 10.1 Deployment; 10.2 Shared, Open Infrastructure; 10.3 Trust; 10.4 On-call Developers; 10.5 Avoiding Blame; 10.6 Conclusion; Chapter 11: How Your Visitors Feel: User-Facing Metrics; 11.1 Why Collect User-Facing Metrics?; 11.2 What Makes a Site Slow?; 11.3 Measuring Delay; 11.4 Building an SLA; 11.5 Visitor Outcomes: Analytics; 11.6 Other Metrics Marketing Cares About; 11.7 How User Experience Affects Web Ops; 11.8 The Future of Web Monitoring; 11.9 Conclusion; Chapter 12: Relational Database Strategy and Tactics for the Web; 12.1 Requirements for Web Databases; 12.2 How Typical Web Databases Grow; 12.3 The Yearning for a Cluster; 12.4 Database Strategy; 12.5 Database Tactics; 12.6 Conclusion; Chapter 13: How to Make Failure Beautiful: The Art and Science of Postmortems; 13.1 The Worst Postmortem; 13.2 What Is a Postmortem?; 13.3 When to Conduct a Postmortem; 13.4 Who to Invite to a Postmortem; 13.5 Running a Postmortem; 13.6 Postmortem Follow-Up; 13.7 Conclusion; Chapter 14: Storage; 14.1 Data Asset Inventory; 14.2 Data Protection; 14.3 Capacity Planning; 14.4 Storage Sizing; 14.5 Operations; 14.6 Conclusion; Chapter 15: Nonrelational Databases; 15.1 NoSQL Database Overview; 15.2 Some Systems in Detail; 15.3 Conclusion; Chapter 16: Agile Infrastructure; 16.1 Agile Infrastructure; 16.2 So, What's the Problem?; 16.3 Communities of Interest and Practice; 16.4 Trading Zones and Apologies; 16.5 Conclusion; Chapter 17: Things That Go Bump in the Night (and How to Sleep Through Them); 17.1 Definitions; 17.2 How Many 9s?; 17.3 Impact Duration Versus Incident Duration; 17.4 Datacenter Footprint; 17.5 Gradual Failures; 17.6 Trust Nobody; 17.7 Failover Testing; 17.8 Monitoring and History of Patterns; 17.9 Getting a Good Night's Sleep; Contributors; Colophon;