October, 2013

It is fitting that our first episode to be split into a TV-esque cliffhanger is with our Netflix panel! In episode 28, we discussed Netflix’s unique engineering culture; in part two, we discuss with the panel the dynamics of how Netflix develops its release engineering tools, Netflix’s cloud prize, configuration management vs. baked potatoes, what percentage of the Internet Netflix actually uses at peak, plus the panel’s guilty (and possibly embarrassing) Netflix pleasures; find out what they are and more when we wrap up:

Why are ops guys in primarily Windows environments looked down upon (or feel looked down upon) in the DevOps community? Very often references will be “oh, and on Windows” like the ops guys running Windows wouldn’t be expected to be as professional as their compatriots on the *nix side of things. How can a primarily Windows ops guy fit in to this DevOps community?

It’s hard to have a conversation or hear a presentation these days about DevOps without hearing Netflix’s name being uttered: they’re a poster-child not only for employing DevOps principles and techniques, but for successfully moving their entire application to Amazon’s Web Services public cloud. But how did they achieve this? And what cultural and technological struggles did they have while reshaping themselves from a company that mails out DVDs to a company that slings bits and produces Emmy-award winning content. Join us for a chat with members of Netflix’s Engineering Tools and Playback Reliability teams; we know it’s a conversation you won’t want to miss… after all: