<?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>Disaster Recovery on Wolkwacht</title>
    <link>https://wolkwacht.nl/tags/disaster-recovery/</link>
    <description>Recent content in Disaster Recovery on Wolkwacht</description>
    <image>
      <title>Wolkwacht</title>
      <url>https://wolkwacht.nl/images/branding/feature-image.png</url>
      <link>https://wolkwacht.nl/images/branding/feature-image.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://wolkwacht.nl/tags/disaster-recovery/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Production Readiness for Dapr on AKS: Upgrades, Disaster Recovery, and Lessons Learned</title>
      <link>https://wolkwacht.nl/posts/production-readiness-dapr-on-aks-upgrades-dr-lessons/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://wolkwacht.nl/posts/production-readiness-dapr-on-aks-upgrades-dr-lessons/</guid>
      <description>&lt;p&gt;&lt;img alt=&#34;A Dapr platform moving safely through upgrade, GitOps, backup, and regional recovery stages&#34; loading=&#34;lazy&#34; src=&#34;https://wolkwacht.nl/images/2026/dapr-production-readiness-feature.svg&#34;&gt;&lt;/p&gt;
&lt;p&gt;Production readiness starts where most tutorials end. Installing Dapr, deploying sidecars, and proving the building blocks are necessary milestones, but they do not answer the operational questions: How will you upgrade without moving every workload at once? Which state must survive a lost cluster? Can another region actually receive traffic? How quickly can you undo a bad change?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
