<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Migrations on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/migrations/</link>
		<description>Recent content in Migrations on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 04 Aug 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/migrations/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Database Migrations in Continuous Delivery</title>
				<link>https://dplabs.tech/blog/database-migrations-continuous-delivery/</link>
				<pubDate>Mon, 04 Aug 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/database-migrations-continuous-delivery/</guid>
				<description>&lt;p&gt;Every CI/CD guide covers application deployment. Very few cover the harder problem: database schema changes in a system that can never be offline.&lt;/p&gt;&#xA;&lt;p&gt;The challenge is that application and database deployments are not atomic. During a rolling or blue-green deployment, old and new application versions run simultaneously against the same database. A migration that&amp;rsquo;s incompatible with the old version causes the old version to fail — precisely during the deployment window when you can least afford failures.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
