I interviewed a few folks on the topic some time ago and published the results here: <a href="https:&#x2F;&#x2F;highops.com&#x2F;insights&#x2F;immutable-infrastructure-6-questions-6-experts&#x2F;" rel="nofollow">https:&#x2F;&#x2F;highops.com&#x2F;insights&#x2F;immutable-infrastructure-6-ques...</a><p>I particularly like the definition that emerged:<p>&#x27;I see it as conceptually dividing your infrastructure into &quot;data&quot; and &quot;everything else&quot;. Data is the stuff that&#x27;s created and modified by the services you&#x27;re providing. The elements of your infrastructure that aren&#x27;t managed by the services can be treated as immutable: you build them, use them, but don&#x27;t make changes to them. If you need to change an infrastructure element, you build a new one and replace the old one&#x27;<p>More in the actual full transcript and in the video