Articles

Engineering notes, written for engineers.

Practical guidance on platform engineering, reliability and delivery: the reasoning, the trade-offs and the configuration. Written to be checked by an experienced engineer.

The examples are generic and illustrative. They are not taken from any client environment: adapt thresholds and settings to your own system.

  1. N—01

    Error budgets and burn-rate alerts: paging for the right reasons

    How to turn an SLO into alerts that fire fast on real outages, stay quiet on noise and stop paging once the problem is fixed.

  2. N—02

    A production baseline for Kubernetes workloads

    Requests, probes, disruption budgets, graceful shutdown and pod security: the settings a production Deployment should have before its first incident.

  3. N—03

    Terraform in a team: state layout, blast radius and reviewed plans

    How to split Terraform state, run plans in CI and apply only what was reviewed, so infrastructure changes become routine instead of risky.

  4. N—04

    Build once, promote by digest: a delivery pipeline you can roll back

    A reference delivery path where the artifact tested in staging is exactly the one in production, and a rollback is a redeploy of the previous digest.

Contact

Want a second opinion on your setup?

Send a short description of your system. A senior engineer replies in writing within one business day.

Discuss your infrastructure