Aller au contenu
Techstream

Vol. IV

Release Engineering & DevSecOps Governance

Progressive delivery, GitOps, the DORA metrics at scale and framework governance

Vol. IV

§ 01, De quoi il s'agit

Progressive delivery, feature flags, GitOps at scale and the governance that makes release orchestration survive an audit. The Release Orchestration Framework is the skeleton; the examples come from my zero-touch release work at SWIFT.

§ 02, Ce que je veux que le lecteur sache faire

  1. 01

    Promote a release through canary stages and roll it back without a meeting.

  2. 02

    Run GitOps for many teams and know when a cluster has drifted from git.

  3. 03

    Explain a release orchestration programme to an auditor with the evidence it produced.

§ 03, Le schéma auquel je reviens toujours

Défile sur le côté →

Canary release and feature flagsload balancer90%10%Stable v1.090% of trafficCanary v1.110%, observedFeature flagscanary-weightonkill-switchoffdark-launchonCanary metricserror ratep99 latency · success rate
Figure, Volume IV: traffic split between a stable release and a canary, with feature flags and the metrics that decide whether it is promoted.

§ 04, Structure prévue

  1. Partie I

    Progressive delivery engineering

    Deployment strategies, automated canary promotion and rollback, and database changes that do not take the service down.

  2. Partie II

    Feature flag architecture

    Kinds of flags, how they are read, the debt they leave behind, and the dark launch as a way to test infrastructure first.

  3. Partie III

    GitOps at Scale

    Repository layout, multi-tenant clusters, secrets under GitOps, and reconciliation when the cluster drifts from git.

  4. Partie IV

    DevSecOps governance

    Running the platform as a product, the DORA (DevOps Research & Assessment) delivery metrics across many teams, and what to build rather than buy.

§ 05, Quand ce sera lisible

Ce volume est en cours d’écriture. Laissez votre e-mail et je vous enverrai un seul message quand il sera lisible.

Un seul e-mail quand ce sera lisible.