|
|
|
|
LEADER |
00000cam a2200000Ia 4500 |
001 |
OR_ocn686711401 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
101129s2010 caua o 001 0 eng d |
040 |
|
|
|a UMI
|b eng
|e pn
|c UMI
|d COO
|d CEF
|d OCLCQ
|d DEBSZ
|d OCLCQ
|d NLE
|d OCLCF
|d OCLCQ
|d EBLCP
|d YDXCP
|d OCLCQ
|d UAB
|d UKAHL
|d OCLCQ
|d OCLCO
|d OCLCQ
|
019 |
|
|
|a 670295052
|a 780425245
|
020 |
|
|
|a 9781449377465
|
020 |
|
|
|a 1449377467
|
020 |
|
|
|a 9781449394158
|
020 |
|
|
|a 1449394159
|
020 |
|
|
|z 9781449377441
|q (pbk.)
|
020 |
|
|
|z 1449377440
|q (pbk.)
|
029 |
1 |
|
|a DEBSZ
|b 355437368
|
029 |
1 |
|
|a DEBSZ
|b 39640250X
|
029 |
1 |
|
|a HEBIS
|b 291508049
|
029 |
1 |
|
|a AU@
|b 000062581814
|
029 |
1 |
|
|a AU@
|b 000066233703
|
035 |
|
|
|a (OCoLC)686711401
|z (OCoLC)670295052
|z (OCoLC)780425245
|
037 |
|
|
|a CL0500000079
|b Safari Books Online
|
050 |
|
4 |
|a QA76.625
|b .W4369 2010
|
082 |
0 |
4 |
|a 006.7
|2 22
|
049 |
|
|
|a UAMI
|
245 |
0 |
0 |
|a Web operations :
|b keeping the data on time /
|c edited by John Allspaw and Jesse Robbins.
|
250 |
|
|
|a 1st ed.
|
260 |
|
|
|a Sebastopol, Calif. :
|b O'Reilly Media,
|c ©2010.
|
300 |
|
|
|a 1 online resource (xvii, 315 pages) :
|b illustrations
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
588 |
0 |
|
|a Print version record.
|
505 |
0 |
|
|a 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.
|
505 |
8 |
|
|a 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.
|
505 |
8 |
|
|a 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.
|
505 |
8 |
|
|a 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.
|
505 |
8 |
|
|a 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.
|
520 |
|
|
|a 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 thri.
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
650 |
|
0 |
|a Internet programming.
|
650 |
|
0 |
|a Web site development.
|
650 |
|
6 |
|a Programmation Internet.
|
650 |
|
6 |
|a Sites Web
|x Développement.
|
650 |
|
7 |
|a Internet programming.
|2 blmlsh
|
650 |
|
7 |
|a Web site development.
|2 blmlsh
|
650 |
|
7 |
|a Internet programming.
|2 fast
|0 (OCoLC)fst00977281
|
650 |
|
7 |
|a Web site development.
|2 fast
|0 (OCoLC)fst01173243
|
700 |
1 |
|
|a Allspaw, John.
|
700 |
1 |
|
|a Robbins, Jesse.
|
776 |
0 |
8 |
|i Print version:
|t Web operations.
|d Beijing [China] ; Sebastopol, Calif. : O'Reilly, 2010
|z 9781449377441
|w (OCoLC)515451109
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781449377465/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH26847907
|
938 |
|
|
|a ProQuest Ebook Central
|b EBLB
|n EBL553592
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 7489318
|
994 |
|
|
|a 92
|b IZTAP
|