Reliability Engineering
posts (16)
- Recovery from the Ground Up: Rollback, PITR, and Returning After Failure2/5
Rolling Back a Release: Code Is the Easy Part
Release rollback often looks like returning to the previous application image. In practice, the hard parts are data, migrations, and side effects that already…
- Deployment Strategies: Why They Exist1/6
Rolling Update: Replacing Pieces Gradually
Rolling update removes downtime during version replacement, but it only works safely when old and new versions can live together for a while.
- series · 6 parts
Deployment Strategies: Why They Exist
Deployment strategies did not appear to make pipelines look serious. They appeared because replacing a version became a moment of risk.
- Recovery from the Ground Up: Rollback, PITR, and Returning After Failure1/5
PITR, RPO, RTO, SLI, SLO, and SLA: A Recovery Vocabulary
Recovery has its own vocabulary, but the important terms describe simple questions: how far back do we go, how much do we lose, how long does it take, and what…
- series · 5 parts
Recovery from the Ground Up: Rollback, PITR, and Returning After Failure
Recovery does not start with a large disaster recovery plan. It starts with a simple question: what exactly do we need to return to, and how much can we lose?
- series · 9 parts
Testing Through Layers: From Code to Infrastructure
This series organizes test types by the place where they catch risk cheapest: from a small code decision to the production environment.