/DevOps

How We Deploy To Production Over 100 Times A Day

- Will Sewell tl;dr: "To achieve this rapid release cadence, we’ve optimised our engineering culture, tooling, and architecture to make the path from idea to production as frictionless as possible, all without sacrificing safety. We believe our approach gets us the best of both worlds: less friction encourages smaller changes, and smaller changes are less risky."

featured in #321

DevSecOps Maturity Model White Paper

tl;dr: Learn about the best practices for assessing and advancing your organization’s DevSecOps maturity. Detect vulnerabilities and deliver digital services with more confidence.

featured in #319

DevSecOps Maturity Model White Paper

tl;dr: A blueprint for assessing and advancing your organization’s DevSecOps practices to detect vulnerabilities and deliver digital services with more confidence.

featured in #293

DevSecOps Maturity Model White Paper

tl;dr: A blueprint for assessing and advancing your organization’s DevSecOps practices to detect vulnerabilities and deliver digital services with more confidence.

featured in #281

A Conversation About How To Enable High-velocity DevOps Culture At Your Organization

- Eira May tl;dr: "How Liberty Mutual implemented a high-performing DevOps culture to increase stability, shorten release cycles, and deliver value faster."

featured in #279

Don't Make My Mistakes: Common Infrastructure Errors I've Made

- Mat Duggan tl;dr: "Allow me a moment to go back through some of the most disastrous decisions or projects I ever agreed to (or even fought to do, sometimes):" (1) Don't migrate an application from the datacenter to the cloud. (2) Don't write your own secrets system. (3) Don't run your own Kubernetes cluster. Mathew runs through 6 decisions in total, and provides what should have been done for each. 

featured in #274

On Making Architectural Decisions

- Evgeniy Nikonorov tl;dr: Here we are shown that the architect’s main task is to define the comprehensive context - a set of evaluation criteria - to make well-balanced architectural decisions, and how to go about doing so.

featured in #252

Service Reliability Math That Every Engineer Should Know

- Matt Rickard tl;dr: "For a service to be up 99.99999% of the time, it can only be down at most 3 seconds every year. Unfortunately, achieving that milestone is a herculean task, even for the most experienced site reliability engineering teams."

featured in #251

How Does FaceTime Work?

- Mat Duggan tl;dr: "We need to establish a connection between two devices through various levels of networking abstraction, both at the ISP level and home level. This needs to be secure, reliable enough to maintain a conversation and also low bandwidth enough to be feasible given modern cellular data limits and home internet data caps. All of this needs to run on a device with limited battery capacity."

featured in #244

No, We Don’t Use Kubernetes

- Maik Zumstrull tl;dr: Maik is commonly asked by customers and interviews if they use Kubernetes as their primary dev platform. He believes the tech is "still very much at the peak of its hype cycle" and details a cost-benefit analysis of it in this post.

featured in #240