• Irreversible Decisions
    • Constraints First
    • Coupling and Cohesion in Practice
    • Trade-off Sliders
    • The Boring Baseline
    • Monolith First, Split on Evidence
    • Service Boundaries That Survive Reorgs
    • Synchronous vs Asynchronous Integration
    • API Contracts and Versioning
    • Idempotency and Retries
    • Choosing a Datastore Without Regret
    • Schema Migrations Without Downtime
    • Consistency Models You Actually Need
    • Caching: The Four Questions
    • Event Sourcing and CDC: When It Pays
    • Trunk-Based Development and Branch Reality
    • Pipeline Design: Fast Feedback, Slow Gates
    • Progressive Delivery
    • Build Reproducibility and Artifact Promotion
    • Rollback Is a Feature
    • Kubernetes: What You Sign Up For
    • Infrastructure as Code That Doesn't Drift
    • Environments, Config, and Secrets
    • Multi-Tenancy and Cost Boundaries
    • The Internal Platform as a Product
    • SLOs, Error Budgets, and Saying No
    • Observability: What to Actually Wire
    • Capacity, Load Shedding, and Backpressure
    • Failure Modes: Timeouts, Breakers, Bulkheads
    • Incident Response and Blameless Postmortems
    • Threat Modeling in One Hour
    • Identity, Authentication, Authorisation
    • Secrets and Key Management
    • Supply Chain: Dependencies, SBOM, Signing
    • Least Privilege and Auditability
    • Architecture Decision Records That Get Read
    • Diagrams That Age Well
    • Runbooks and On-Call Docs
    • Design Reviews and RFCs
    • Building a Team Architecture Memory
    • GitHub
  • to navigate
  • to select
  • to close
    • Home
    • Delivery and CI/CD
    On this page
    rocket_launch

    Delivery and CI/CD

    How code gets from a laptop to production without drama: branching, pipelines, progressive rollout, and rollback.

    account_tree

    Trunk-Based Development and Branch Reality

    Long-lived branches are inventory. Inventory hides risk and the bill arrives at merge time.

    conveyor_belt

    Pipeline Design: Fast Feedback, Slow Gates

    Order your pipeline by cost of feedback, not by category of test.

    trending_up

    Progressive Delivery

    Deploy and release are different events. Separating them is the cheapest risk reduction available.

    inventory_2

    Build Reproducibility and Artifact Promotion

    If you cannot rebuild last week's release byte-for-byte, you cannot debug it or prove what shipped.

    undo

    Rollback Is a Feature

    Time to recover matters more than time between failures. Design the undo path before you need it.

    © 2026 Architecture Field Notes. Built with Lotus Docs