June 2010
Intermediate to advanced
338 pages
10h 33m
English
Content preview from Web OperationsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
On-call Developers
One of the most common misconceptions about separating operations from development is that it requires members of the operations team to be the only ones who work on fixing production issues. This setup avoids the development interruptions that cause delays to new features but insulates developers from the realities of code running in a 24/7 production environment.
So far in this chapter we've discussed the need for operations to trust that developers have their best interests in mind, that developers should be allowed to deploy code without formal approval processes, and that developers should have access to production systems. This works only if developers take on responsibility for fixing problems with their code in production, which means they need to be on call.
At Flickr, the operations team operates a standard primary/backup pager rotation. In almost all cases, it's a known failure scenario and the on-call engineer can resolve the issue with a well-understood playbook. But every so often there's an issue the on-call engineer can't debug or fix by himself. In these cases, he'll call one of the developers for help.
This environment creates some useful social dynamics. As anyone who has carried a pager knows, avoiding being paged at 3:00 a.m. on a Sunday is a powerful incentive to keep things from breaking and to make sure ops has all the tools it needs to fix a problem without you. As an example, Flickr has a shared IRC channel; it's very common to see something ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.