devops

Howard Abrams demonstrates, in an EmacsConf 2015 talk, how he uses org-mode's Babel and Tramp to configure and operate remote servers from a single document. Code blocks, their results and the explanatory text all live together.

A podcast episode of Arrested DevOps with Andrew Clay Shafer and Bryan Cantrill, featuring Cantrill's rant on integrity in companies and technology.

John Allspaw and Paul Hammond's Velocity 09 talk on how Flickr achieved ten or more deploys per day through close cooperation between development and operations.

Bryan Cantrill's GOTO Chicago 2017 talk on debugging production systems under pressure, centered on the incident where an operator's mistyped command rebooted an entire Joyent datacenter. It covers human factors, automation and architecture.

A fasterthanlime video essay arguing that GitHub Actions is a poorly designed system, with a history of personal computing and CI, and a look at how it works behind the scenes. It is sponsored by Brilliant.

Jesse Newland describes how GitHub uses Hubot, its chat bot, to run operations such as deployment, monitoring, graphing and provisioning from chat rooms. He explains how this improves shared awareness and remote work culture.

Rick Houlihan's AWS re:Invent 2018 deep dive on advanced DynamoDB design patterns. It covers index overloading, GSI sharding, composite keys, graph processing and transactions.

Liz Rice live-codes a minimal container runtime in a few lines of Go at GOTO Amsterdam 2018. She explains namespaces, control groups and what a host knows about its containers.

Overclocker der8auer tours Hetzner's Falkenstein data center in Germany, showing custom racks, own mainboards, passively cooled servers and ATX-style cases on shelves.

Bryan Cantrill's Uptime 2017 talk on the engineering challenges of the stateful data path, including storage, firmware and hardware bugs. It uses the 'zebras vs. horses' diagnostic heuristic to explain why rare failures keep appearing.

Daniel Azuma's ElixirConf 2018 talk on whether Docker and OTP conflict. He shows they can coexist and uses Horde and DeltaCrdt, with a live tank-game demo, to keep state alive across container kills.

Liz Rice builds a container from scratch in about 100 lines of Go, showing that a container is not a lightweight VM but a set of Linux kernel features and flags.

Nickolas Means recounts the 1979 Three Mile Island accident minute by minute, from the control rod insertion to the operator's decision to switch off emergency cooling. He argues that finding systemic causes is more useful than blaming individuals.

Dr. Richard Cook, a physician and patient safety researcher, presents his ideas on how complex systems fail, at Velocity 2012. He argues for designing for resiliency rather than trying to exhaustively handle every failure mode.

Benn Jordan investigates infrasound and low-frequency noise from data centers, including xAI's Colossus and a crypto mine, and reports his own experiments on the effects. The video covers the health and community impacts on nearby residents.

Jon Moore's Strange Loop 2017 talk argues that rate limiting is the wrong tool for protecting services from noisy clients. He proposes concurrency-based capacity management and quotas instead.

Jérôme Petazzoni explains how Linux containers are built from kernel features like cgroups, namespaces and SELinux. He demonstrates putting the pieces together by hand to make a container and compares runtimes and approaches like jails and zones.

Eric Brandwine's AWS re:Invent 2015 session on how Amazon VPC networking works. It covers the problems the design solved, why traditional approaches do not scale, and the mechanisms used for customer isolation and VPC endpoints.

Bryan Cantrill's Velocity NYC 2015 talk argues for running containers directly on bare metal rather than layering them on virtual machines. He covers the history of containers and how SmartOS runs Linux workloads via syscall emulation.

Dave Plummer tours the IBM z16 mainframe from design through factory assembly, test lab, accelerators and water cooling. He explains why mainframes still exist and what makes them reliable.

A Business Insider investigation into the US boom in AI data centers, mapping where they are, who owns them, and how much power and water they consume. It looks at the costs borne by communities, with a focus on Virginia.

Kyle Drake of Neocities explains the bandwidth pricing pitfalls of the big cloud providers. He describes how to run high-volume, bandwidth-heavy infrastructure far more cheaply, including through co-location.

Jared Mauch tells how he got fed up with poor internet options in rural Michigan and built his own fiber network to his town. The talk was given at NLNOG Live in September 2020.

A walkthrough of installing Synapse, Riot and Jitsi from scratch on Debian to run your own Matrix communication service. The description warns it is now quite outdated and links to updated material.

Mikey Dickerson's keynote at Velocity NY 2014, one year after the healthcare.gov launch failure. He recounts how a small team rescued the site and what the episode showed about government IT contracting.

Kelsey Hightower introduces Kubernetes to sysadmins at PuppetConf 2016, with a demo. He explains the declarative model and how it changes the contract between infrastructure and applications.

Rick Reed of WhatsApp speaks at MeetBSD about running a messaging service on FreeBSD and Erlang at huge scale. He covers the stack, tuning and the challenges of millions of connections per host.

Michael Bryzek of Flow gives a QCon London 2018 talk on key decisions for building maintainable microservices. It covers infrastructure, continuous deployment, communication, event streaming and language choice.

Scott Manley examines why SpaceX, Google and others are looking at orbital data centers. He walks through the economics, heat rejection and solar power arguments, with links to the Lumen/Starcloud and Google Suncatcher papers.

A dotScale 2014 talk by Robert Kennedy, a former healthcare.gov SRE who later worked at Google, about the engineering effort to rescue the troubled site. It explains the technical and organizational problems behind the failed launch.

James Hamilton, AWS VP and distinguished engineer, gives an insider view of the innovations behind the AWS cloud at re:Invent 2014. He covers custom hardware, networking, regions and availability zones, and infrastructure at scale.

An AWS re:Invent 2018 session in which Holly Mesrobian and Marc Brooker explain how AWS Lambda is built, including its sandboxing, isolation and scaling architecture. It covers what happens under the hood when serverless code runs.

Jessie Frazelle's DockerCon SF 2015 talk on running Docker containers for desktop applications, with fun container hacks and images. It shows how far containers can be pushed beyond servers.

An AWS re:Invent 2018 talk on how AWS limits the blast radius of failures. It covers design techniques such as cell-based architecture and shuffle sharding.

An AWS re:Invent 2018 session on how DynamoDB was built as a hyper-scale NoSQL database. It discloses underpinnings of the service and how it is run for over 100,000 customers.

The official Kubernetes documentary, part 1, tells how a handful of Google engineers, inspired by Docker's success, built a container orchestrator. It covers the internal resistance to open source and the competition of the container orchestrator wars.

A PyCon 2013 block of Friday evening lightning talks. It includes the debut of Hy, a Lisp dialect that compiles to Python AST, and Solomon Hykes's first public talk on Docker.

An AWS re:Invent 2019 session for advanced DynamoDB users on design patterns used by large customers, including Amazon retail. It covers GSI sharding, index overloading, graph processing, composite keys and transactional workflows.

John Graham-Cumming of Cloudflare talks at dotScale 2015 about handling roughly 10 trillion log lines a month. The talk touches on Cloudflare's hardware, its logging stack and its use of Lua in Nginx.

An AWS re:Invent 2014 talk on the core distributed systems primitives behind AWS and Amazon.com, such as consensus, key-value stores and transactional logging. It describes how AWS builds large services from a few common building blocks.