mirror of
https://github.com/hanzoai/skills.git
synced 2026-11-19 00:47:36 +00:00
hanzoskills.com/llms.txt now opens with the install line, the API reference index and the company index, so an agent that lands on any one of the three can find the rest. robots.txt claimed 537 documents while llms.txt counts 920. The number is gone from robots.txt; llms.txt derives it. public/ is regenerated from scripts/site.py, which it had fallen behind: the copy-prompt menu and agent bar were in the generator and not in the committed pages. tests/site.mjs passes against the result. Co-authored-by: Hanzo Dev <[email protected]>
632 lines
31 KiB
HTML
632 lines
31 KiB
HTML
<!doctype html>
|
|
<html lang="en"><head>
|
|
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
|
|
<title>engineering-deployment-strategies</title>
|
|
<meta name="color-scheme" content="dark">
|
|
<style>
|
|
/* Committed to one visual world: a dark instrument panel. No light variant —
|
|
the dot field and the hairline rules only read on black, and a naive
|
|
inversion would wash both out. Every colour is painted explicitly so the page
|
|
never borrows a host background. */
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
|
|
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
|
|
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
|
|
|
|
:root{
|
|
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
|
|
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
|
|
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
|
|
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
|
|
--font-zen-pixel-square:'Zen Pixel Square',monospace;
|
|
--mono:var(--font-zen-mono);
|
|
--sans:var(--font-zen-sans);
|
|
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
|
|
--r:999px; --r-soft:14px;
|
|
}
|
|
*{box-sizing:border-box}
|
|
html{-webkit-text-size-adjust:100%}
|
|
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
|
|
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
|
|
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
|
|
|
|
/* The dot field. A halftone made of one repeating radial-gradient, faded out
|
|
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
|
|
/* No overflow clip here: the dot field is inset to the box already, and a clip
|
|
would cut off the copy-prompt menu. */
|
|
.hero{position:relative;border-bottom:1px solid var(--line)}
|
|
.hero::before{content:"";position:absolute;inset:0;
|
|
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
|
|
background-size:7px 7px;
|
|
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
|
|
pointer-events:none}
|
|
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
|
|
|
|
nav{border-bottom:1px solid var(--line)}
|
|
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
|
|
justify-content:space-between;align-items:center;gap:1rem}
|
|
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--ink);text-decoration:none;
|
|
display:inline-flex;align-items:center;gap:.6rem}
|
|
.brand i{font-style:normal;color:var(--faint)}
|
|
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
|
|
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
|
|
text-transform:uppercase;color:var(--soft);text-decoration:none}
|
|
nav a.up:hover{color:var(--ink)}
|
|
|
|
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
|
|
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
|
|
h1 em{font-style:normal;color:var(--faint)}
|
|
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
|
|
|
|
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
|
|
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
|
|
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
|
|
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
|
|
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
|
|
line-height:1.2;font-weight:400}
|
|
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
|
|
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
|
|
.btn.solid:hover{background:#d8d8d4}
|
|
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
|
|
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
|
|
|
|
/* Copy-prompt selector. Each row copies the prompt for its own target. */
|
|
.copy{position:relative;display:inline-flex}
|
|
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
|
|
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
|
|
padding:.4rem;display:flex;flex-direction:column;
|
|
box-shadow:0 12px 32px rgba(0,0,0,.75)}
|
|
.menu[hidden]{display:none}
|
|
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
|
|
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
|
|
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
|
|
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
|
|
white-space:nowrap}
|
|
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
|
|
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
|
|
.mi:hover .mark{color:var(--ink)}
|
|
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
|
|
letter-spacing:.1em;text-transform:uppercase}
|
|
|
|
/* Works-with bar: one scrolling row, name and mark per agent. */
|
|
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
|
|
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
|
|
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
|
|
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
|
|
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
|
|
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
|
|
display:flex;align-items:center}
|
|
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
|
|
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
|
|
-webkit-overflow-scrolling:touch;
|
|
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
|
|
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
|
|
.bar::-webkit-scrollbar{display:none}
|
|
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
|
|
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
|
|
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
|
|
text-decoration:none;background:var(--ground)}
|
|
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
|
|
.agent .mark{width:.95rem;height:.95rem}
|
|
|
|
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
|
|
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
|
|
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
|
|
p{margin:0 0 1rem;max-width:70ch}
|
|
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
|
|
li{margin:.22rem 0}
|
|
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
|
|
text-decoration-color:var(--line-hi)}
|
|
a:hover{text-decoration-color:var(--ink)}
|
|
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
|
|
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
|
|
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
|
|
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
|
|
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
|
|
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
|
|
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
|
|
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
|
|
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
|
|
display:block;overflow-x:auto}
|
|
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
|
|
|
|
.curl{display:block;background:var(--panel);border:1px solid var(--line);
|
|
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
|
|
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
|
|
white-space:pre;line-height:1.9}
|
|
.curl b{color:var(--ink);font-weight:400}
|
|
.curl i{font-style:normal;color:var(--faint)}
|
|
|
|
/* index */
|
|
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
|
|
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
|
|
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
|
|
#q:focus{outline:none;border-color:var(--soft)}
|
|
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
|
|
text-transform:uppercase;margin:0 0 2rem}
|
|
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
|
|
padding-bottom:.45rem}
|
|
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
|
|
border-radius:var(--r-soft);text-decoration:none}
|
|
.row:hover{background:#0a0a0a}
|
|
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
|
|
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
|
|
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
|
|
color:var(--faint);font-size:.85rem}
|
|
footer a{color:var(--soft)}
|
|
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
|
|
margin:0 0 2rem;font-size:.85rem}
|
|
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
|
|
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
|
|
border-bottom:1px solid var(--line);padding-bottom:.4rem}
|
|
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
|
|
.fmap a:hover{text-decoration:underline}
|
|
.fmap div{color:var(--faint);line-height:1.5}
|
|
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
|
|
|
|
@media (max-width:640px){
|
|
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
|
|
.btns{gap:.5rem}
|
|
.btn{padding:.75rem 1.15rem;font-size:.68rem}
|
|
.copy,.copy .btn{width:100%;justify-content:center}
|
|
.menu{left:0;right:0;min-width:0}
|
|
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
|
|
.strip b{border-right:0;padding-right:0}
|
|
.bar{width:100%}
|
|
}
|
|
</style>
|
|
<link rel="alternate" type="text/markdown" href="/engineering-deployment-strategies.md">
|
|
|
|
<link rel="icon" href="/favicon.svg">
|
|
<link rel="canonical" href="https://hanzoskills.com/engineering-deployment-strategies">
|
|
</head>
|
|
<!-- Reading this with a machine? Every page here is also plain markdown.
|
|
This one: https://hanzoskills.com/engineering-deployment-strategies.md
|
|
Index: https://hanzoskills.com/llms.txt
|
|
Corpus: https://hanzoskills.com/all.md
|
|
Append .md to any path for the markdown twin. -->
|
|
<body>
|
|
<nav><div class="in">
|
|
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
|
|
<a class="up" href="/">All skills</a>
|
|
</div></nav>
|
|
|
|
<div class="wrap">
|
|
<h1>engineering-deployment-strategies</h1><p class="lede">Production deployment strategies including blue-green, canary, rolling updates, zero-downtime deployments, and database migrations</p><h1>Deployment Strategies</h1>
|
|
<p><strong>Scope</strong>: Comprehensive deployment patterns, progressive delivery, feature flags, rollback procedures, and database migration strategies across Kubernetes, cloud platforms, and containerized environments</p>
|
|
<p><strong>Lines</strong>: ~650</p>
|
|
<p><strong>Last Updated</strong>: 2025-10-27</p>
|
|
<p><strong>Format Version</strong>: 1.0 (Atomic)</p>
|
|
<hr>
|
|
<h2>When to Use This Skill</h2>
|
|
<p>Activate this skill when:</p>
|
|
<ul><li>Designing deployment pipelines for production systems</li><li>Implementing zero-downtime deployments</li><li>Setting up progressive delivery (canary, blue-green)</li><li>Planning database schema migrations</li><li>Configuring rollback procedures</li><li>Implementing feature flags for gradual rollouts</li><li>Designing traffic shifting strategies</li><li>Setting up deployment validation and health checks</li></ul>
|
|
<p>Don't use this skill for:</p>
|
|
<ul><li>Basic CI/CD pipeline setup (see <code>continuous-integration.md</code>)</li><li>Container orchestration basics (see <code>kubernetes-deployment</code>)</li><li>Infrastructure provisioning (see <code>terraform-best-practices</code>)</li></ul>
|
|
<hr>
|
|
<h2>Core Concepts</h2>
|
|
<h3>Concept 1: Deployment Strategy Selection</h3>
|
|
<p><strong>Definition</strong>: Choose deployment approach based on risk tolerance, downtime requirements, and infrastructure capabilities</p>
|
|
<p><strong>Decision Matrix</strong>:</p>
|
|
<pre><code>Requirement | Recommended Strategy
|
|
---------------------|--------------------
|
|
Zero downtime | Blue-Green, Canary, Rolling
|
|
Instant rollback | Blue-Green
|
|
Gradual validation | Canary
|
|
Limited resources | Rolling, Recreate
|
|
Complex migrations | Blue-Green + Feature Flags
|
|
High risk changes | Canary + A/B Testing</code></pre>
|
|
<p><strong>Key Principles</strong>:</p>
|
|
<ol><li>Understand blast radius of failures</li><li>Plan for rollback scenarios</li><li>Validate before full deployment</li><li>Monitor metrics during rollout</li><li>Maintain backward compatibility</li></ol>
|
|
<p><strong>Benefits</strong>:</p>
|
|
<ul><li>Reduced deployment risk</li><li>Faster time to production</li><li>Improved reliability</li><li>Better user experience</li></ul>
|
|
<hr>
|
|
<h3>Concept 2: Progressive Delivery</h3>
|
|
<p><strong>Definition</strong>: Gradually release changes with continuous validation and control</p>
|
|
<p><strong>Components</strong>:</p>
|
|
<pre><code>Code → Deploy → Feature Flag → Observe → Decide
|
|
↓ ↓ ↓ ↓
|
|
Containers Control Metrics Expand/
|
|
Exposure Rollback</code></pre>
|
|
<p><strong>Traffic Management Patterns</strong>:</p>
|
|
<ul><li><strong>Percentage-based</strong>: Route X% of traffic to new version</li><li><strong>User-based</strong>: Route specific users/groups to canary</li><li><strong>Geography-based</strong>: Route by region for localized testing</li><li><strong>Header-based</strong>: Route based on request headers (internal testing)</li></ul>
|
|
<p><strong>Validation Strategy</strong>:</p>
|
|
<ol><li>Deploy to canary environment</li><li>Route small traffic percentage</li><li>Monitor error rates, latency, business metrics</li><li>Gradually increase traffic</li><li>Promote or rollback based on metrics</li></ol>
|
|
<hr>
|
|
<h3>Concept 3: Database Migration Strategies</h3>
|
|
<p><strong>Definition</strong>: Evolve database schema without breaking application deployments</p>
|
|
<p><strong>Expand-Contract Pattern</strong>:</p>
|
|
<pre><code>Phase 1: EXPAND
|
|
├─ Add new schema alongside old
|
|
├─ Deploy app with dual writes
|
|
└─ Both versions work
|
|
|
|
Phase 2: MIGRATE
|
|
├─ Backfill new schema
|
|
└─ Verify data integrity
|
|
|
|
Phase 3: CONTRACT
|
|
├─ Deploy app using only new schema
|
|
├─ Remove old schema
|
|
└─ Cleanup</code></pre>
|
|
<p><strong>Backward Compatibility Rules</strong>:</p>
|
|
<ul><li>Add columns as nullable first</li><li>Never drop columns during deployment</li><li>Use views for compatibility layers</li><li>Dual write during transitions</li><li>Batch backfill operations</li></ul>
|
|
<p><strong>Rollback Considerations</strong>:</p>
|
|
<ul><li>Keep old schema during rollback window</li><li>Test rollback procedures</li><li>Document migration dependencies</li><li>Use transactions where possible</li></ul>
|
|
<hr>
|
|
<h2>Patterns</h2>
|
|
<h3>Pattern 1: Blue-Green Deployment</h3>
|
|
<p><strong>Problem</strong>: Need instant rollback capability with zero downtime</p>
|
|
<p><strong>Kubernetes Implementation</strong>:</p>
|
|
<pre><code class="lang-yaml"># Two identical deployments
|
|
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: myapp-blue
|
|
spec:
|
|
replicas: 3
|
|
selector:
|
|
matchLabels:
|
|
app: myapp
|
|
version: blue
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: myapp
|
|
version: blue
|
|
spec:
|
|
containers:
|
|
- name: myapp
|
|
image: myapp:v1.0.0
|
|
readinessProbe:
|
|
httpGet:
|
|
path: /ready
|
|
port: 8080
|
|
---
|
|
# Service switches between blue and green
|
|
apiVersion: v1
|
|
kind: Service
|
|
metadata:
|
|
name: myapp
|
|
spec:
|
|
selector:
|
|
app: myapp
|
|
version: blue # Change to 'green' to switch
|
|
ports:
|
|
- port: 80
|
|
targetPort: 8080</code></pre>
|
|
<p><strong>Switch Procedure</strong>:</p>
|
|
<pre><code class="lang-bash"># 1. Deploy green environment
|
|
kubectl apply -f deployment-green.yaml
|
|
|
|
# 2. Wait for green to be ready
|
|
kubectl wait --for=condition=available deployment/myapp-green
|
|
|
|
# 3. Test green environment
|
|
curl http://myapp-green-preview/health
|
|
|
|
# 4. Switch traffic to green
|
|
kubectl patch service myapp -p '{"spec":{"selector":{"version":"green"}}}'
|
|
|
|
# 5. Monitor for issues (keep blue running)
|
|
sleep 600
|
|
|
|
# 6. Scale down blue (after validation)
|
|
kubectl scale deployment myapp-blue --replicas=0</code></pre>
|
|
<p><strong>Benefits</strong>: Instant rollback, full testing before switch <strong>Trade-offs</strong>: Requires 2x infrastructure, database complexity</p>
|
|
<hr>
|
|
<h3>Pattern 2: Canary Deployment with Flagger</h3>
|
|
<p><strong>Problem</strong>: Need gradual validation with automatic rollback</p>
|
|
<p><strong>Flagger Canary Resource</strong>:</p>
|
|
<pre><code class="lang-yaml">apiVersion: flagger.app/v1beta1
|
|
kind: Canary
|
|
metadata:
|
|
name: myapp
|
|
spec:
|
|
targetRef:
|
|
apiVersion: apps/v1
|
|
kind: Deployment
|
|
name: myapp
|
|
provider: istio
|
|
analysis:
|
|
interval: 1m
|
|
threshold: 5
|
|
maxWeight: 50
|
|
stepWeight: 10
|
|
metrics:
|
|
- name: request-success-rate
|
|
thresholdRange:
|
|
min: 99
|
|
interval: 1m
|
|
- name: request-duration
|
|
thresholdRange:
|
|
max: 500
|
|
interval: 1m</code></pre>
|
|
<p><strong>Progressive Rollout</strong>:</p>
|
|
<pre><code>5% → Monitor → 15% → Monitor → 25% → Monitor → 50% → Complete
|
|
↓ ↓ ↓ ↓
|
|
Healthy? Healthy? Healthy? Healthy?
|
|
↓ ↓ ↓ ↓
|
|
Continue Continue Continue Promote
|
|
or or or or
|
|
Rollback Rollback Rollback Rollback</code></pre>
|
|
<p><strong>Benefits</strong>: Minimal blast radius, data-driven decisions <strong>Trade-offs</strong>: Slower deployment, complex traffic management</p>
|
|
<hr>
|
|
<h3>Pattern 3: Rolling Update with Health Checks</h3>
|
|
<p><strong>Problem</strong>: Need zero downtime with limited resources</p>
|
|
<p><strong>Kubernetes Configuration</strong>:</p>
|
|
<pre><code class="lang-yaml">apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: myapp
|
|
spec:
|
|
replicas: 10
|
|
strategy:
|
|
type: RollingUpdate
|
|
rollingUpdate:
|
|
maxUnavailable: 1 # Max 1 pod down at a time
|
|
maxSurge: 2 # Allow 2 extra pods during update
|
|
template:
|
|
spec:
|
|
terminationGracePeriodSeconds: 60
|
|
containers:
|
|
- name: myapp
|
|
image: myapp:v2.0.0
|
|
readinessProbe:
|
|
httpGet:
|
|
path: /ready
|
|
port: 8080
|
|
failureThreshold: 2
|
|
livenessProbe:
|
|
httpGet:
|
|
path: /health
|
|
port: 8080
|
|
failureThreshold: 3
|
|
lifecycle:
|
|
preStop:
|
|
exec:
|
|
command: ["/bin/sh", "-c", "sleep 15"]</code></pre>
|
|
<p><strong>Update Process</strong>:</p>
|
|
<ol><li>Create 1 new pod (within maxSurge)</li><li>Wait for readiness probe to pass</li><li>Terminate 1 old pod</li><li>Wait for graceful shutdown</li><li>Repeat until all pods updated</li></ol>
|
|
<p><strong>Benefits</strong>: No extra infrastructure, gradual rollout <strong>Trade-offs</strong>: Slower than blue-green, mixed versions during deployment</p>
|
|
<hr>
|
|
<h3>Pattern 4: Database Expand-Contract Migration</h3>
|
|
<p><strong>Problem</strong>: Need to change database schema without breaking deployments</p>
|
|
<p><strong>Implementation</strong>:</p>
|
|
<pre><code class="lang-sql">-- PHASE 1: EXPAND (v1.1 app deployment)
|
|
ALTER TABLE orders ADD COLUMN status_name VARCHAR(50) NULL;
|
|
|
|
CREATE TRIGGER sync_status
|
|
BEFORE INSERT OR UPDATE ON orders
|
|
FOR EACH ROW
|
|
EXECUTE FUNCTION sync_order_status();
|
|
|
|
-- PHASE 2: MIGRATE (background job)
|
|
UPDATE orders
|
|
SET status_name = CASE status
|
|
WHEN 0 THEN 'pending'
|
|
WHEN 1 THEN 'processing'
|
|
WHEN 2 THEN 'completed'
|
|
END
|
|
WHERE status_name IS NULL;
|
|
|
|
-- PHASE 3: CONTRACT (v1.2 app deployment)
|
|
ALTER TABLE orders ALTER COLUMN status_name SET NOT NULL;
|
|
ALTER TABLE orders DROP COLUMN status;</code></pre>
|
|
<p><strong>Application Evolution</strong>:</p>
|
|
<pre><code>v1.0: Reads/writes old column
|
|
v1.1: Reads old, writes both (dual write)
|
|
v1.2: Reads/writes new column only
|
|
v1.3: Old column removed</code></pre>
|
|
<p><strong>Benefits</strong>: Zero downtime, rollback-safe <strong>Trade-offs</strong>: Multi-phase deployment, temporary overhead</p>
|
|
<hr>
|
|
<h3>Pattern 5: Feature Flag Controlled Rollout</h3>
|
|
<p><strong>Problem</strong>: Decouple deployment from release</p>
|
|
<p><strong>Implementation</strong>:</p>
|
|
<pre><code class="lang-python">from launchdarkly import LDClient
|
|
|
|
ld_client = LDClient("sdk-key")
|
|
|
|
def get_pricing_page(user_id):
|
|
user = {
|
|
"key": user_id,
|
|
"custom": {
|
|
"deployment_version": os.getenv("APP_VERSION"),
|
|
"canary_group": os.getenv("CANARY_GROUP")
|
|
}
|
|
}
|
|
|
|
# Feature flag controls which version user sees
|
|
use_new_pricing = ld_client.variation("new-pricing", user, False)
|
|
|
|
if use_new_pricing:
|
|
return render_template("pricing_v2.html")
|
|
else:
|
|
return render_template("pricing_v1.html")</code></pre>
|
|
<p><strong>Targeting Rules</strong>:</p>
|
|
<pre><code class="lang-json">{
|
|
"flagKey": "new-pricing",
|
|
"targeting": [
|
|
{
|
|
"variation": 1,
|
|
"values": ["canary"],
|
|
"attribute": "canary_group"
|
|
},
|
|
{
|
|
"variation": 1,
|
|
"percentage": {
|
|
"variations": [
|
|
{"variation": 0, "weight": 95000},
|
|
{"variation": 1, "weight": 5000}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
}</code></pre>
|
|
<p><strong>Benefits</strong>: Deploy code safely, control feature exposure, instant rollback <strong>Trade-offs</strong>: Code complexity, flag management overhead</p>
|
|
<hr>
|
|
<h2>Anti-Patterns</h2>
|
|
<h3>Anti-Pattern 1: No Rollback Plan</h3>
|
|
<p><strong>Problem</strong>: Deploying without tested rollback procedures</p>
|
|
<p><strong>Why It's Bad</strong>:</p>
|
|
<ul><li>Panic during incidents</li><li>Extended downtime</li><li>Data loss risks</li><li>Manual recovery errors</li></ul>
|
|
<p><strong>Solution</strong>:</p>
|
|
<pre><code class="lang-bash"># Document and test rollback
|
|
# Blue-Green: Switch back
|
|
kubectl patch service myapp -p '{"spec":{"selector":{"version":"blue"}}}'
|
|
|
|
# Rolling: Rollback deployment
|
|
kubectl rollout undo deployment/myapp
|
|
|
|
# Database: Keep old schema during rollback window
|
|
# Feature Flags: Kill switch</code></pre>
|
|
<hr>
|
|
<h3>Anti-Pattern 2: Testing in Production Only</h3>
|
|
<p><strong>Problem</strong>: No pre-deployment validation</p>
|
|
<p><strong>Why It's Bad</strong>:</p>
|
|
<ul><li>Discover issues after user impact</li><li>No safety net</li><li>Higher risk</li></ul>
|
|
<p><strong>Solution</strong>:</p>
|
|
<pre><code class="lang-yaml"># Smoke tests before full rollout
|
|
- name: Test green environment
|
|
run: |
|
|
GREEN_URL=$(get_green_url)
|
|
curl -f $GREEN_URL/health
|
|
curl -f $GREEN_URL/api/test
|
|
./load-test.sh $GREEN_URL</code></pre>
|
|
<hr>
|
|
<h3>Anti-Pattern 3: Incompatible Schema Changes</h3>
|
|
<p><strong>Problem</strong>: Breaking old application version with schema changes</p>
|
|
<p><strong>Why It's Bad</strong>:</p>
|
|
<ul><li>Forces all-or-nothing deployment</li><li>Can't rollback</li><li>Downtime required</li></ul>
|
|
<p><strong>Solution</strong>: Use expand-contract pattern, maintain backward compatibility</p>
|
|
<hr>
|
|
<h3>Anti-Pattern 4: No Health Checks</h3>
|
|
<p><strong>Problem</strong>: Routing traffic to unhealthy instances</p>
|
|
<p><strong>Why It's Bad</strong>:</p>
|
|
<ul><li>User-facing errors</li><li>Failed deployments go undetected</li><li>No automatic recovery</li></ul>
|
|
<p><strong>Solution</strong>:</p>
|
|
<pre><code class="lang-yaml">readinessProbe:
|
|
httpGet:
|
|
path: /ready
|
|
port: 8080
|
|
failureThreshold: 2
|
|
livenessProbe:
|
|
httpGet:
|
|
path: /health
|
|
port: 8080
|
|
failureThreshold: 3</code></pre>
|
|
<hr>
|
|
<h3>Anti-Pattern 5: Manual Deployment Steps</h3>
|
|
<p><strong>Problem</strong>: Undocumented manual interventions</p>
|
|
<p><strong>Why It's Bad</strong>:</p>
|
|
<ul><li>Not reproducible</li><li>Error-prone</li><li>Knowledge silos</li><li>Can't automate</li></ul>
|
|
<p><strong>Solution</strong>: Automate everything, document runbooks, use GitOps</p>
|
|
<hr>
|
|
<h2>Quick Reference</h2>
|
|
<h3>Deployment Strategy Comparison</h3>
|
|
<p>| Strategy | Downtime | Rollback | Cost | Complexity | |----------|----------|----------|------|------------| | Recreate | High | Slow | Low | Low | | Rolling | None | Medium | Low | Medium | | Blue-Green | None | Instant | High (2x) | Medium | | Canary | None | Fast | Medium | High |</p>
|
|
<h3>Health Check Best Practices</h3>
|
|
<pre><code class="lang-yaml"># Liveness: Is app alive?
|
|
livenessProbe:
|
|
httpGet:
|
|
path: /health
|
|
port: 8080
|
|
initialDelaySeconds: 30
|
|
periodSeconds: 10
|
|
failureThreshold: 3
|
|
|
|
# Readiness: Can app serve traffic?
|
|
readinessProbe:
|
|
httpGet:
|
|
path: /ready
|
|
port: 8080
|
|
initialDelaySeconds: 10
|
|
periodSeconds: 5
|
|
failureThreshold: 2</code></pre>
|
|
<h3>Graceful Shutdown</h3>
|
|
<pre><code class="lang-python">import signal
|
|
import sys
|
|
|
|
def handle_shutdown(signum, frame):
|
|
print("Shutting down gracefully...")
|
|
# Stop accepting new requests
|
|
server.close()
|
|
# Wait for existing requests
|
|
time.sleep(10)
|
|
sys.exit(0)
|
|
|
|
signal.signal(signal.SIGTERM, handle_shutdown)</code></pre>
|
|
<h3>Database Migration Checklist</h3>
|
|
<ul><li>[ ] Schema changes are backward compatible</li><li>[ ] Dual write implemented during transition</li><li>[ ] Backfill plan for existing data</li><li>[ ] Rollback procedure documented</li><li>[ ] Migration tested in staging</li><li>[ ] Monitoring for data consistency</li></ul>
|
|
<hr>
|
|
<h2>Level 3: Resources</h2>
|
|
<p><strong>Extended documentation, production-ready examples, and automation tools</strong></p>
|
|
<h3>REFERENCE.md</h3>
|
|
<p><strong>Location</strong>: <code>resources/REFERENCE.md</code> (4,033 lines)</p>
|
|
<p>Comprehensive reference covering:</p>
|
|
<ul><li>Deployment strategy deep-dive (blue-green, canary, rolling, recreate)</li><li>Progressive delivery patterns and feature flags</li><li>Rollback procedures and automation</li><li>Zero-downtime deployment techniques</li><li>Database migration strategies (expand-contract, shadow tables)</li><li>Kubernetes deployment patterns with Istio/Flagger</li><li>Cloud provider deployment strategies (AWS, GCP, Azure)</li><li>Traffic management and load balancing</li><li>Monitoring and observability during deployments</li><li>Testing strategies and validation</li><li>Complete code examples for all patterns</li></ul>
|
|
<h3>Scripts</h3>
|
|
<p><strong>validate_deployment.py</strong> (600+ lines) Validates deployment configuration files across multiple platforms:</p>
|
|
<pre><code class="lang-bash"># Validate Kubernetes manifests
|
|
./validate_deployment.py --file deployment.yaml
|
|
|
|
# Check entire directory
|
|
./validate_deployment.py --directory k8s/ --type kubernetes
|
|
|
|
# JSON output for CI/CD
|
|
./validate_deployment.py --file deployment.yaml --json</code></pre>
|
|
<p><strong>execute_canary.py</strong> (550+ lines) Executes automated canary deployments with progressive traffic shifting:</p>
|
|
<pre><code class="lang-bash"># Kubernetes canary deployment
|
|
./execute_canary.py --platform kubernetes --service myapp --version v2.0
|
|
|
|
# AWS ALB canary
|
|
./execute_canary.py --platform aws-alb --service myapp --version v2.0
|
|
|
|
# Custom configuration
|
|
./execute_canary.py --config canary-config.yaml --json</code></pre>
|
|
<p><strong>test_deployment.sh</strong> (400+ lines) Tests deployment processes and measures downtime:</p>
|
|
<pre><code class="lang-bash"># Monitor deployment and measure downtime
|
|
./test_deployment.sh --url https://myapp.com --duration 300
|
|
|
|
# Test specific strategy
|
|
./test_deployment.sh --url https://myapp.com --strategy blue-green --json</code></pre>
|
|
<h3>Production Examples</h3>
|
|
<p><strong>Blue-Green Deployments</strong>:</p>
|
|
<ul><li><code>examples/blue-green/kubernetes-blue-green.yaml</code>: Complete K8s blue-green setup with health checks, PDB, and HPA</li><li><code>examples/docker/docker-compose-blue-green.yml</code>: Docker Compose blue-green with NGINX load balancer</li></ul>
|
|
<p><strong>Canary Deployments</strong>:</p>
|
|
<ul><li><code>examples/canary/flagger-canary.yaml</code>: Flagger + Istio progressive canary with Prometheus metrics</li><li><code>examples/github-actions/canary-deployment-workflow.yml</code>: GitHub Actions automated canary pipeline</li></ul>
|
|
<p><strong>Rolling Updates</strong>:</p>
|
|
<ul><li><code>examples/rolling/kubernetes-rolling-update.yaml</code>: Production-ready rolling update with proper health checks and resource limits</li></ul>
|
|
<p><strong>Database Migrations</strong>:</p>
|
|
<ul><li><code>examples/database-migration/expand-contract-migration.sql</code>: Complete expand-contract pattern with PostgreSQL</li></ul>
|
|
<p>All examples include:</p>
|
|
<ul><li>Production-ready configurations</li><li>Comprehensive comments</li><li>Health check implementations</li><li>Rollback procedures</li><li>Monitoring integration</li><li>Security best practices</li></ul>
|
|
<hr>
|
|
<h2>Related Skills</h2>
|
|
<ul><li><code>continuous-integration.md</code> - CI pipeline design</li><li><code>test-driven-development.md</code> - Testing strategies</li><li><code>technical-debt.md</code> - Managing deployment complexity</li><li><code>cloud-kubernetes-deployment</code> - Kubernetes specifics</li><li><code>terraform-best-practices</code> - Infrastructure provisioning</li></ul>
|
|
<hr>
|
|
<p><strong>Last Updated</strong>: 2025-10-27 <strong>Maintainer</strong>: Skills Team <strong>Validation</strong>: CI-validated, production-tested patterns</p>
|
|
<footer>
|
|
<div class="fmap">
|
|
<div><b>Build</b>
|
|
<a href="https://hanzo.app">hanzo.app</a> app builder
|
|
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
|
|
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
|
|
<div><b>Run</b>
|
|
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
|
|
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
|
|
<div><b>Account</b>
|
|
<a href="https://hanzo.id">hanzo.id</a> sign in
|
|
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
|
|
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
|
|
<div><b>Company</b>
|
|
<a href="https://hanzo.ai">hanzo.ai</a> canonical
|
|
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
|
|
</div>
|
|
<div class="fend"><a href="/engineering-deployment-strategies.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
|
|
</footer>
|
|
</div></body></html> |