DevOps Industry Updates #27: Hiatus Edition

Welcome back! Since the last issue, there has been a major development in my personal life. I inherited a new, highly-complex distributed system that’s under active development and needs constant attention. In other words, I became a Dad! To make sure I can dedicate the time needed to be the best co-parent possible, I am pausing DevOps Industry Updates for a little while. Stay tuned though, I will be back, and with more original content!

🔥 Top Cream

This issue’s top 5 stories:

  1. Reasons why bugs might feel “impossible”
  2. Sloth
  3. Navigating the 8 fallacies of distributed computing
  4. Zero downtime Postgres migration, done right
  5. Ness

🌎 Society

  • 2021 DevOps Trends – What We Learned From 450 Engineering Teams: Humanitec has collected a lot of data from engineering teams about their DevOps setup. Their analysis provides insights into the tooling most teams use, how they approach application configuration management and infrastructure configuration management, which DevOps metrics they measure and what we can learn from these metrics.

  • 2021 SRE Report: Catchpoint’s annual report analyzed survey responses from over 300 site reliability engineers globally across a range of industries and company sizes. It reveals a wide range of fascinating insights and concludes with an actionable path for SREs to consistently deliver customer value.

📟 DevOps

🛠️ DevOps Tools

  • Sloth: easy and simple Prometheus SLO (service level objectives) generator.

  • A Vim Guide For Veteran Users

  • Toward Vagrant 3.0: in order to support its growing ecosystem and community as we move toward the 3.0 release, we are making changes to Vagrant that will maintain its Ruby-based features while being ported to Go.

  • Ness: deploy web sites and apps to your own cloud account effortlessly.

  • StarQueue: a free hosted HTTP message queue.

☸️ Kubernetes

  • Devtron: an open source software delivery workflow for Kubernetes written in Go.

  • 13 Best Practices for using Helm: Helm is an indispensable tool for deploying applications to Kubernetes clusters. But it is only by following best practices that you’ll truly reap the benefits of Helm. Here are 13 best practices to help you create, operate, and upgrade applications using Helm.

  • Kubernetes Learning Path: “since Kubernetes is growing very rapidly, online tutorials, books are getting easily outdated, but most of the information is available on the official website. So I have made an effort to collate all the important topics with links that provide the learning path for Beginners to get started with Kubernetes.”

🔐 Security

💻 Programming

  • The Cost of 100% Reliability: the more reliability you want, the more it costs, with a rule of thumb that each additional 9 of reliability (eg. moving from 99% to 99.9% reliability) costs 10 times more to achieve. But what contributes to that cost increase?

🐧 Linux

🚢 Leadership

☁️ Cloud

  • The Cost of Cloud, a Trillion Dollar Paradox

  • Seven guiding principles of serverless systems: the big question in serverless design is how do you know your team is doing it correctly? Serverless can feel fuzzy, and best practices don’t feel so obvious. The good news is that there are some fundamental principles that can help you navigate your journey.

  • Navigating the 8 fallacies of distributed computing: the fallacies of distributed computing are a list of 8 statements describing false assumptions that architects and developers involved with distributed systems might make (but should undoubtedly steer away from). In this blog post, we’ll look at what these fallacies are, how they came to be, and how to navigate them in order to engineer dependable distributed systems.


Article version: 1.0.0

Written on June 29, 2021