View profile

Devops Week News - Issue #80

Revue
 
This week we bring you Viktor's presentation about Building a Self-Sufficient System.  In the article
 

Devops Week News

March 20 · Issue #80 · View online
Weekly newsletter with curated articles about DevOps.

This week we bring you Viktor’s presentation about Building a Self-Sufficient System.
 In the article section, we have Analysis of a Kubernetes a hack, a curated list of awesome kubernetes sources, should I Rust, or should I Go, autoscaling DynamoDB, updating a 50 terabyte Postgresql database, Bitbucket Pipelines vs. Jenkins Pipeline and the hidden costs of serverless.
What about contributing to the next newsletter? Send us links, events, DevOps job-related, etc., via @devopsweeknews.

Video of the week
DevOps Gathering 2018 | Building A Self-Sufficient System by Victor Farcic - YouTube
Defining the steps required for a design of a self-adapting and self-healing system that will continue operating efficiently even when we are on vacations.
What do we expect from a modern cluster? If a replica fails, it should be brought back up (rescheduled). If a node goes down all the services that were running inside it should be distributed among healthy nodes. Those tasks are easy to accomplish. Schedulers (Swarm, Kubernetes, Mesos/Marathon, and so on) are already doing those things for us. Many solutions provide self-healing by making sure that the system is (almost) always in the desired state. The problem with self-healing is that it does not take into the account constant changes. The number of requests is continuously changing, errors are created, network bandwidth is fluctuating, and so on. A cluster, and services inside it, is like a living body that needs to adapt to changes continuously. Services need to be scaled and de-scaled, nodes need to be created and added to the cluster only to be removed soon after. We call that process adaptation. Even that is not the problem in itself, as long as we have an army of operators that will monitor the system and do reactive and preventive actions. How about converting adaptation into self-adaptation? Can we remove humans from the process and make a system that is self-sufficient? The goal of this talk is to try to outline the steps required for a design of a self-adapting and self-healing system that will continue operating efficiently even when we are on vacations.
Articles
Analysis of a Kubernetes hack — Backdooring through kubelet
GitHub - ramitsurana/awesome-kubernetes
Should I Rust, or Should I Go – codeburst
Auto Scaling: With Amazon DynamoDB, It’s As Easy As 1-2-3 - N2WS
Updating a 50 terabyte PostgreSQL database – Adyen Tech – Medium
Bitbucket Pipelines vs Jenkins Pipeline – Hacker Noon
The hidden costs of serverless – Amiram Shachar – Medium
Let's have fun!
We wish you a great week!
Did you enjoy this issue?
If you don't want these updates anymore, please unsubscribe here
If you were forwarded this newsletter and you like it, you can subscribe here
Powered by Revue