Cargando…
Web operations : keeping the data on time /
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 applic...
| Clasificación: | Libro Electrónico |
|---|---|
| Otros Autores: | , |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Sebastopol, Calif. :
O'Reilly Media,
©2010.
|
| Edición: | 1st ed. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Foreword; Preface; 1Web Operations: The Career; Theo Schlossnagle; Why Does Web Operations Have It Tough?; From Apprentice to Master; Conclusion; 2How Picnik Uses Cloud Computing: Lessons Learned; Justin Huff; Where the Cloud Fits (and Why!); Where the Cloud Doesn't Fit (for Picnik); Conclusion; 3Infrastructure and Application Metrics; John Allspaw, with Matt Massie; Time Resolution and Retention Concerns; Locality of Metrics Collection and Storage; Layers of Metrics; Providing Context for Anomaly Detection and Alerts; Log Lines Are Metrics, Too.
- Correlation with Change Management and Incident TimelinesMaking Metrics Available to Your Alerting Mechanisms; Using Metrics to Guide Load-Feedback Mechanisms; A Metrics Collection System, Illustrated: Ganglia; Conclusion; 4Continuous Deployment; Eric Ries; Small Batches Mean Faster Feedback; Small Batches Mean Problems Are Instantly Localized; Small Batches Reduce Risk; Small Batches Reduce Overhead; The Quality Defenders' Lament; Getting Started; Continuous Deployment Is for Mission-Critical Applications; Conclusion; 5Infrastructure As Code; Adam Jacob; Service-Oriented Architecture.
- Conclusion6Monitoring; Patrick Debois; Story: "The Start of a Journey"; Step 1: Understand What You Are Monitoring; Step 2: Understand Normal Behavior; Step 3: Be Prepared and Learn; Conclusion; 7How Complex Systems Fail; John Allspaw and Richard Cook; How Complex Systems Fail; Further Reading; 8Community Management and Web Operations; Heather Champ and John Allspaw; 9Dealing with Unexpected Traffic Spikes; Brian Moon; How It All Started; Alarms Abound; Putting Out the Fire; Surviving the Weekend; Preparing for the Future; CDN to the Rescue; Proxy Servers; Corralling the Stampede.
- Streamlining the CodebaseHow Do We Know It Works?; The Real Test; Lessons Learned; Improvements Since Then; 10Dev and Ops Collaboration and Cooperation; Paul Hammond; Deployment; Shared, Open Infrastructure; Trust; On-call Developers; Avoiding Blame; Conclusion; 11How Your Visitors Feel: User-Facing Metrics; Alistair Croll and Sean Power; Why Collect User-Facing Metrics?; What Makes a Site Slow?; Measuring Delay; Building an SLA; Visitor Outcomes: Analytics; Other Metrics Marketing Cares About; How User Experience Affects Web Ops; The Future of Web Monitoring; Conclusion.
- 12Relational Database Strategy and Tactics for the WebBaron Schwartz; Requirements for Web Databases; How Typical Web Databases Grow; The Yearning for a Cluster; Database Strategy; Database Tactics; Conclusion; 13How to Make Failure Beautiful: The Art and Science of Postmortems; Jake Loomis; The Worst Postmortem; What Is a Postmortem?; When to Conduct a Postmortem; Who to Invite to a Postmortem; Running a Postmortem; Postmortem Follow-Up; Conclusion; 14Storage; Anoop Nagwani; Data Asset Inventory; Data Protection; Capacity Planning; Storage Sizing; Operations; Conclusion.