<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Operational-Resilience on Digital sovereignty, thought through</title><link>https://mguenther.nl/tags/operational-resilience/</link><description>Recent content in Operational-Resilience on Digital sovereignty, thought through</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://mguenther.nl/tags/operational-resilience/index.xml" rel="self" type="application/rss+xml"/><item><title>Can Sovereignty Make You Less Resilient?</title><link>https://mguenther.nl/series/can-sovereignty-make-you-less-resilient/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://mguenther.nl/series/can-sovereignty-make-you-less-resilient/</guid><description>&lt;p&gt;Sovereignty done right makes you resilient. But sovereignty you don&amp;rsquo;t operate is the opposite: a risk. You move a workload in-house to be more sovereign. Your jurisdiction, your rules, no outside provider in the loop. More control – which is the whole point.&lt;/p&gt;
&lt;p&gt;But the provider you left wasn&amp;rsquo;t only running the service. They were also keeping it up, patching it, and making sure you could still reach it when something broke. You didn&amp;rsquo;t see that part, because you never had to.&lt;/p&gt;</description></item></channel></rss>