/DevOps

"As Code"

- Mitchell Hashimoto tl;dr: I've always personally defined the "as code" suffix in "X as Code" to mean "a system of principles or rules". This is in contrast to the popular interpretation of "as code" to mean "as programming."

featured in #596

11 Monitoring Requirements For Enterprise DevOps Teams

tl;dr: Isaac Johnson, a Principal Software Engineer and DevOps Architect with experience at multiple Fortune 500 companies, reveals the key capabilities he looks for when evaluating monitoring platforms for enterprise DevOps teams. He offers a candid look at common monitoring pain points and discusses how to overcome them.

featured in #593

4 Quick Steps For Better Incident Resolution In DevOps

tl;dr: Accelerate your time to resolution and build resilience into your systems with this simple 4-step approach. This guide outlines critical best practices for ensuring your organization’s response to incidents is as efficient and effective as possible.

featured in #583

4 Quick Steps For Better Incident Resolution In DevOps

tl;dr: Accelerate your time to resolution and build resilience into your systems with this simple 4-step approach. This guide outlines critical best practices for ensuring your organization’s response to incidents is as efficient and effective as possible.

featured in #583

Odin: Uber’s Stateful Platform

- Jesper Borlum Gianluca Mezzetti tl;dr: “The Odin platform aims to provide a unified operational experience by encompassing all aspects of managing stateful workloads. These aspects include host lifecycle, workload scheduling, cluster management, monitoring, state propagation, operational user interfaces, alerting, auto-scaling, and automation. Uber deploys stateful systems at global, regional, and zonal levels, and Odin is designed to manage these systems consistently and in a technology-agnostic manner.” This post provides an overview of Odin’s origins, the fundamental principles, and the challenges encountered early on. 

featured in #534

The State Of DevSecOps

tl;dr: An analysis of tens of thousands of applications and container images across thousands of cloud environments. This report assesses the security posture of applications today and evaluates the adoption of best practices that are at the core of DevSecOps—infrastructure as code, automated cloud deployments, secure application development practices, and more.

featured in #523

The State Of DevSecOps

tl;dr: An analysis of tens of thousands of applications and container images across thousands of cloud environments. This report assesses the security posture of applications today and evaluates the adoption of best practices that are at the core of DevSecOps—infrastructure as code, automated cloud deployments, secure application development practices, and more.

featured in #523

The DevSecOps Maturity Model

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 #496

Modern DevOps Transformation Begins With Static Code Analysis

tl;dr: Many organizations implementing DevOps are facing significant underperformance issues. Learn how integrating Sonar static code analysis solutions can address these transformative issues, propelling organizations towards more efficient and secure software development and improving the efficiency of the current DevOps processes.

featured in #490

The Scary Thing About Automating Deploys

- Sean McIlroy tl;dr: Sean delves into the complexities and strategies of automating deployments at scale, focusing on how Slack transitioned from manual oversight to using their automated tool for deployment processes in a high-change environment. “When people talk about continuous deployment, they’re often thinking about deploying to systems as soon as changes are ready. They talk about microservices and 2-pizza teams (~8 people). But what does continuous deployment mean when you’re looking at 150 changes on a normal day? That’s a lot of pizzas…" 

featured in #482