<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Deployment on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/deployment/</link>
		<description>Recent content in Deployment on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 12 May 2025 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Deployment Strategies: Blue/Green, Canary, and Rolling Deployments</title>
				<link>https://dplabs.tech/blog/deployment-strategies/</link>
				<pubDate>Mon, 12 May 2025 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/deployment-strategies/</guid>
				<description>&lt;p&gt;A deployment strategy is not just a technical implementation detail. It determines how much risk you take with each release, how quickly you can recover from problems, and what infrastructure you need to support it. Choosing without understanding the trade-offs is choosing accidentally.&lt;/p&gt;&#xA;&lt;h2 id=&#34;rolling-deployments-the-default&#34;&gt;Rolling Deployments: The Default&lt;/h2&gt;&#xA;&lt;p&gt;Rolling deployments incrementally replace old instances with new ones. At any point during the deployment, both old and new versions are running simultaneously.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
