A web application involves many specialists, but it takes people in web ops to ensure that everything works together throughout an application's lifetime. It's the expertise you need when your start-up gets an unexpected spike in web traffic, or when a new feature causes your mature application to fail. In this collection of essays and interviews, web veterans such as Theo Schlossnagle, Baron Schwartz, and Alistair Croll offer insights into this evolving field. You'll learn stories from the trenches--from builders of some of the biggest sites on the Web--on what's necessary to help a site thrive.
Learn the skills needed in web operations, and why they're gained through experience rather than schooling
Understand why it's important to gather metrics from both your application and infrastructure
Consider common approaches to database architectures and the pitfalls that come with increasing scale
Learn how to handle the human side of outages and degradations
Find out how one company avoided disaster after a huge traffic deluge
Discover what went wrong after a problem occurs, and how to prevent it from happening again
Contributors include:
John Allspaw
Heather Champ
Michael Christian
Richard Cook
Alistair Croll
Patrick Debois
Eric Florenzano
Paul Hammond
Justin Huff
Adam Jacob
Jacob Loomis
Matt Massie
Brian Moon
Anoop Nagwani
Sean Power
Eric Ries
Theo Schlossnagle
Baron Schwartz
Andrew Shafer
About the Author John Allspaw is currently Operations Engineering Manager at Flickr, the popular photo site. He has had extensive experience working with growing web sites since 1999. These include online news magazines Salon.com, InfoWorld.com, Macworld.com and social networking sites that experienced extreme growth (Friendster and Flickr). During his time at Friendster, traffic increased 5X. He was responsible for their transition from a couple dozen servers in a failing data center to over 400 machines across two data centers, and the complete redesign of the backing infrastructure. When he joined Flickr, they had 10 servers in a tiny data center in Vancouver; they are now located in multiple data centers across the US. Prior to his web experience, Allspaw worked in modeling and simulation as a mechanical engineer doing car crash simulations for the NHTSA.
Jesse Robbins (@jesserobbins) is CEO of Opscode (makers of Chef) and a recognized expert in Infrastructure, Web Operations, and Emergency Management.
He serves as co-chair of the Velocity Web Performance & Operations Conference and contributes to the O'Reilly Radar . Prior to co-founding Opscode, he worked at Amazon.com with a title of "Master of Disaster" where he was responsible for Website Availability for every property bearing the Amazon brand.
Robbins is a volunteer Firefighter/EMT and Emergency Manager, and led a task force deployed in Operation Hurricane Katrina. His experiences in the fire service profoundly influence his efforts in technology, and he strives to distill his knowledge from these two worlds and apply it in service of both.
Foreword 13
Preface 15
1 Web Operations: The Career 21
Theo Schlossnagle 21
Why Does Web Operations Have It Tough? 22
From Apprentice to Master 24
Conclusion 29
2 How Picnik Uses Cloud Computing: Lessons Learned 31
Justin Huff 31
Where the Cloud Fits (and Why!) 32
Where the Cloud Doesn’t Fit (for Picnik) 40
Conclusion 40
3 Infrastructure and Application Metrics 41
John Allspaw, with Matt Massie 41
Time Resolution and Retention Concerns 42
Locality of Metrics Collection and Storage 43
Layers of Metrics 44
Providing Context for Anomaly Detection and Alerts 47
Log Lines Are Metrics, Too 48
Correlation with Change Management and Incident Timelines 50
Making Metrics Available to Your Alerting Mechanisms 51
Using Metrics to Guide Load-Feedback Mechanisms 52
A Metrics Collection System, Illustrated: Ganglia 56
Conclusion 67
4 Continuous Deployment 69
Eric Ries 69
Small Batches Mean Faster Feedback 69
Small Batches Mean Problems Are Instantly Localized 70
Small Batches Reduce Risk 70
Small Batches Reduce Overhead 71
The Quality Defenders’ Lament 72
Getting Started 76
Continuous Deployment Is for Mission-Critical Applications 80
Conclusion 83
5 Infrastructure As Code 85
Adam Jacob 85
Service-Oriented Architecture 87
Conclusion 99
6 Monitoring 101
Patrick Debois 101
Story: “The Start of a Journey” 101
Step 1: Understand What You Are Monitoring 105
Step 2: Understand Normal Behavior 115
Step 3: Be Prepared and Learn 122
Conclusion 126
7 How Complex
Systems Fail 127
John Allspaw and Richard Cook 127
How Complex Systems Fail 128
Further Reading 136
8 Community Management and Web Operations 137
Heather Champ and John Allspaw 137
9 Dealing with Unexpected Traffic Spikes 147
Brian Moon 147
How It All Started 147
Alarms Abound 148
Putting Out the Fire 149
Surviving the Weekend 150
Preparing for the Future 151
CDN to the Rescue 151
Proxy Servers 152
Corralling the Stampede 152
Streamlining the Codebase 153
How Do We Know It Works? 154
The Real Test 155
Lessons Learned 156
Improvements Since Then 156
10 Dev and Ops Collaboration and Cooperation 159
Paul Hammond 159
Deployment 160
Shared, Open Infrastructure 164
Trust 166
On-call Developers 168
Avoiding Blame 173
Conclusion 175
11 How Your Visitors Feel: User-Facing Metrics 177
Alistair Croll and Sean Power 177
Why Collect User-Facing Metrics? 179
What Makes a Site Slow? 183
Measuring Delay 185
Building an SLA 191
Visitor Outcomes: Analytics 193
Other Metrics Marketing Cares About 198
How User Experience Affects Web Ops 199
The Future of Web Monitoring 200
Conclusion 205
12 Relational Database Strategy and Tactics for the Web 207
Baron Schwartz 207
Requirements for Web Databases 208
How Typical Web Databases Grow 213
The Yearning for a Cluster 220
Database Strategy 225
Database Tactics 232
Conclusion 238
13 How to Make Failure Beautiful: The Art and
Science of Postmortems 239
Jake Loomis 239
The Worst Postmortem 240
What Is a Postmortem? 241
When to Conduct a Postmortem 242
Who to Invite to a Postmortem 243
Running a Postmortem 243
Postmortem Follow-Up 244
Conclusion 246
14 Storage 247
Anoop Nagwani 247
Data Asset Inventory 247
Data Protection 251
Capacity Planning 260
Storage Sizing 262
Operations 264
Conclusion 265
15 Nonrelational Databases 267
Eric Florenzano 267
NoSQL Database Overview 268
Some Systems in Detail 272
Conclusion 281
16 Agile Infrastructure 283
Andrew Clay Shafer 283
Agile Infrastructure 285
So, What’s the Problem? 289
Communities of Interest and Practice 299
Trading Zones and Apologies 299
Conclusion 302
17 Things That Go Bump in the Night (and How to Sleep Through Them) 305
Mike Christian 305
Definitions 307
How Many 9s? 308
Impact Duration Versus Incident Duration 309
Datacenter Footprint 310
Gradual Failures 311
Trust Nobody 312
Failover Testing 312
Monitoring and History of Patterns 313
Getting a Good Night’s Sleep 314
Contributors 317
Index 323
Programming

motw/Web Operations_ Keeping the Data on Time - John Allspaw.pdf

lgli/John Allspaw & Jesse Robbins - Web Operations: Keeping the Data on Time (2010, O'Reilly).pdf

zlib/Computers/Networking/John Allspaw & Jesse Robbins/Web Operations: Keeping the Data on Time_21446032.pdf

Robbins, Jesse; Allspaw, John

Allspaw, John, Robbins, Jesse

1st ed., Beijing [China], Sebastopol, CA, China, 2010

United States, United States of America

1. Aufl, Beijing ; Köln, 2010

1, PS, 2010

producers:
Adobe PDF Library 9.0

Memory of the World Librarian: marcell mars

"Learn the skills needed in web operations, and why they're gained through experience rather than schooling; understand why it's important to gather metrics from both your application and your infrastructure; consider common approaches to database architectures and the pitfalls that come with increasing scale; learn how to handle the human side of outages and degradation; find out how one company avoided disaster after a huge traffic deluge; discover--after a problem occurs--what went wrong and how to prevent it from happening again"--P. [4] of cover.
Includes index.

Learn what it takes to build and maintain high-traffic websites with Web Operations. Featuring essays from today's top web veterans, this insightful book shows you how to run your web ops as reliably and effectively as Google, Microsoft, and Yahoo run theirs. Even if your site never gets that big, you'll profit from the experience and knowledge of the people who created sites for these and other industry giants. http://oreilly.com/catalog/0636920000136

Featuring essays from today's top web engineers, this insightful book shows you how to run your web operations as reliably and effectively as Google, Microsoft, and Yahoo! run theirs. Even if your site never gets that big, you'll profit from the experience and knowledge of the people who created sites for these and other industry giants

2022-05-01