About

In-depth technical articles on SRE, platform engineering, and infrastructure.

We publish long-form pieces that go deep on containers, Linux internals, observability, production systems, and the platforms that run them. Same approach every time: read the specs, run the real tools, capture the output, and explain what is actually happening.

The Mission

A lot of SRE and infrastructure writing stays at a high level. We focus on the concrete details — the file formats, command output, kernel constraints, and the bytes that make up running systems.

Every example is executed on real hardware. We show the exact commands, the complete unedited terminal output, and direct links to the authoritative specifications — so you can run the identical steps yourself and verify every result.

Target Audience

This publication is built specifically for professionals who manage systems at scale:

• Site Reliability Engineers (SREs) looking for deep root-cause analysis over surface-level tutorials.
• Platform Engineers & Architects designing infrastructure primitives and continuous delivery systems.
• Systems Engineers who need to understand deep kernel constraints and unexpected failure modes.

Core Pillars

• Observability & Telemetry (Metrics, tracing, logging) — the signals that remain useful when systems are under load or failing.
• Resilience & Chaos Engineering (Failure domains, incident mitigation) — understanding how things break and keeping services running through it.
• Infrastructure & Automation (IaC, immutable deployments) — the real mechanics of container runtimes, deployments, and platform changes.
• Performance Tuning (Latency, kernel metrics, scaling) — measuring and adjusting from first principles, not guesses.

Site Architecture & Philosophy

Static site generated with Jekyll, styled with Tailwind. Minimal JavaScript. The only third-party services are Google Analytics 4 and AdSense. See our Privacy Policy for details.

We keep pages small and fast. The content should load quickly even when your network is having a bad day.

Get in touch

Questions, corrections, or ideas: [email protected]

Published by the onlysre.dev Team.