<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Infrastructure on dplabs — Software Engineering &amp; Technology Consultancy</title>
		<link>https://dplabs.tech/tags/infrastructure/</link>
		<description>Recent content in Infrastructure on dplabs — Software Engineering &amp; Technology Consultancy</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://dplabs.tech/tags/infrastructure/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Immutable Infrastructure vs Configuration Management: Choosing Your Operations Model</title>
				<link>https://dplabs.tech/blog/immutable-infrastructure/</link>
				<pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
				<guid>https://dplabs.tech/blog/immutable-infrastructure/</guid>
				<description>&lt;p&gt;Two schools of thought in infrastructure management have different answers to the same question: when the configuration of a server needs to change, what do you do?&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Configuration management&lt;/strong&gt; answer: connect to the server and change it. Tools like Ansible, Puppet, and Chef automate this process.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Immutable infrastructure&lt;/strong&gt; answer: build a new server with the desired configuration, route traffic to it, terminate the old one. The server itself is never modified after provisioning.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
