Sysadmins for sysadmins

Seems like sound principles and suggestions

The single Postgres setting that almost took down our database

About Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at:

About tradeoffs

By Julia Evans. Nice walkthrough on learning and troubleshooting, using DNS as example.

Even if you are not using AWS - there is a ton of info to learn from.

Excellent article on http load balancing by @[email protected]

Some food for thinking

Something to think about

Good article on understanding caching

Interesting observations on how OpenAI uses Kubernetes

Atsibodo virtualios IT konferencijos? Mums taip pat. Todėl jau ši balandį norime Tave pakviesti į jau antrą kartą vyksiantį DevOps forumą "DevOps in Shorts".

Interesting info on how Uber operates it's infrastructure.

There is no such system that will not fail, so the question - how?

Talks about failure domains, fault isolation and testing it (using chaos engineering)

How to think about these systems

Actually quite good insights

cross-posted from [email protected]: https://group.lt/post/46385

Adopting DevOps practices is nowadays a recurring task in the industry. DevOps is a set of practices intended to reduce the friction between the software development (Dev) and the IT operations (Ops), resulting in higher quality software and a shorter development lifecycle. Even though many resources are talking about DevOps practices, they are often inconsistent with each other on the best DevOps practices. Furthermore, they lack the needed detail and structure for beginners to the DevOps field to quickly understand them.

In order to tackle this issue, this paper proposes four foundational DevOps patterns: Version Control Everything, Continuous Integration, Deployment Automation, and Monitoring. The patterns are both detailed enough and structured to be easily reused by practitioners and flexible enough to accommodate different needs and quirks that might arise from their actual usage context. Furthermore, the patterns are tuned to the DevOps principle of Continuous Improvement by containing metrics so that practitioners can improve their pattern implementations.

The article does not describes but actually identified and included 2 other patterns in addition to the four above (so actually 6):

• Cloud Infrastructure, which includes cloud computing, scaling, infrastructure as a code, ...
• Pipeline, "important for implementing Deployment Automation and Continuous Integration, and segregating it from the others allows us to make the solutions of these patterns easier to use, namely in contexts where a pipeline does not need to be present."

The paper is interesting for the following structure in describing the patterns:

• Name: An evocative name for the pattern.
• Context: Contains the context for the pattern providing a background for the problem.
• Problem: A question representing the problem that the pattern intends to solve.
• Forces: A list of forces that the solution must balance out.
• Solution: A detailed description of the solution for our pattern’s problem.
• Consequences: The implications, advantages and trade-offs caused by using the pattern.
• Related Patterns: Patterns which are connected somehow to the one being described.
• Metrics: A set of metrics to measure the effectiveness of the pattern’s solution implementation.

Some Terraform practices

I remember when reverse tunnel was a security issue - now it is widely used!

Tracing back to the root

Are you doing a new trend already?

reliability capabilities in gcp

Simple intro into port scanning and a little bit on detection

So... the house of cards is starting to fall?

Such and similar events always remind me two readings:

How complex systems fail and Why Do Computers Stop and What Can Be Done About It?

can this be prevented? I don't think so, but what could be done? Check this book - Antifragile