WeSearch

Expand-Contract Pattern vs Blue-Green Deployment for PostgreSQL Schema Migrations

·4 min read · 0 reactions · 0 comments · 3 views
Expand-Contract Pattern vs Blue-Green Deployment for PostgreSQL Schema Migrations

Compare two major strategies for zero-downtime schema changes. Expand-contract: add new column, migrate data, drop old. Blue-green: run two schemas in parallel, switch traffic. Show when to use which, with PostgreSQL-specific examples.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3790305) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SoftwareDevs mvpfactory.io Posted on May 1 • Originally published at mvpfactory.io Expand-Contract Pattern vs Blue-Green Deployment for PostgreSQL Schema Migrations #webdev #programming --- title: "Expand-Contract vs Blue-Green: PostgreSQL Zero-Downtime Migrations" published: true description: "Compare expand-contract pattern and blue-green deployment for PostgreSQL schema migrations.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)