# Sre
All Sre notes →1 — Continuous Integration
Merging and testing changes continuously so integration problems surface in minutes, not in the multi-day merge conflict that used to be normal.
10 — Supply Chain Security
SBOMs, artifact signing, and provenance attestation — verifying what's actually being deployed is what was actually built, not something injected in between.
2 — Continuous Delivery
Keeping every merged change in a deployable state, which is the precondition every other release-engineering practice in this Part builds on.
3 — Deployment Strategies
The spectrum from all-at-once to fully progressive rollout, and the blast-radius-vs-speed trade-off each point on that spectrum makes.
4 — Blue-Green Deployments
Running two full production environments and switching traffic between them atomically — instant rollback, at the cost of running double the infrastructure.
5 — Canary Releases
Shipping a change to a small traffic slice first and watching its SLIs before a full rollout — the deployment strategy error budgets were built to gate.
6 — Feature Flags
Decoupling deploy from release so a bad feature can be turned off in seconds instead of requiring a rollback — and the flag-debt that accumulates if they're never cleaned up.
7 — Progressive Delivery
Combining canaries, feature flags, and automated analysis into a single rollout pipeline that promotes or rolls back on its own based on live SLI data.
8 — Rollbacks
Why 'roll back' has to be a tested, fast, boring operation — the incident-response tool you only find out is broken during the incident where you need it.
9 — Release Automation
Removing the manual, error-prone steps from a release so the process is identical — and equally safe — at 2pm on a Tuesday and 2am during an incident.