<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog — Opsburg</title>
    <link>https://opsburg.dev/blog</link>
    <description>News from the Opsburg workshop: keeping a cloud up and running, platform engineering, SRE and why we turned it into a city-builder game.</description>
    <language>en</language>
    <lastBuildDate>Wed, 28 Oct 2026 07:00:00 GMT</lastBuildDate>
    <atom:link href="https://opsburg.dev/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Doing it by hand versus a control plane</title>
      <link>https://opsburg.dev/blog/by-hand-versus-a-control-plane</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/by-hand-versus-a-control-plane</guid>
      <pubDate>Wed, 28 Oct 2026 07:00:00 GMT</pubDate>
      <description>You can manage micro frontend versions with a JSON file and a script. Here is exactly what that costs, and the point where it stops being the cheap option.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>Self-hosting micro frontends: a compliance-first guide</title>
      <link>https://opsburg.dev/blog/self-hosting-micro-frontends-compliance</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/self-hosting-micro-frontends-compliance</guid>
      <pubDate>Wed, 21 Oct 2026 07:00:00 GMT</pubDate>
      <description>In a regulated environment the first question is not how it scales, but where the data lives and who can prove it. What self-hosting has to answer.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>Do you actually need micro frontends?</title>
      <link>https://opsburg.dev/blog/do-you-actually-need-micro-frontends</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/do-you-actually-need-micro-frontends</guid>
      <pubDate>Wed, 14 Oct 2026 07:00:00 GMT</pubDate>
      <description>Micro frontends solve an organisational problem before a technical one. If you do not have that problem, they mostly add work. An honest checklist.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>Module Federation with Vite in production: what changes</title>
      <link>https://opsburg.dev/blog/module-federation-vite-production</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/module-federation-vite-production</guid>
      <pubDate>Wed, 07 Oct 2026 07:00:00 GMT</pubDate>
      <description>Module Federation works with Vite, but dev and build take different paths, and the gap is where production surprises come from. What to expect.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>One build, every environment: runtime configuration for micro frontends</title>
      <link>https://opsburg.dev/blog/one-build-every-environment</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/one-build-every-environment</guid>
      <pubDate>Wed, 30 Sep 2026 07:00:00 GMT</pubDate>
      <description>If your pipeline builds the same code once per environment, the artifact you tested is not the artifact you ship. Here is how to build once instead.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>How to roll back a micro frontend in 30 seconds (without rebuilding the host)</title>
      <link>https://opsburg.dev/blog/roll-back-a-micro-frontend-in-30-seconds</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/roll-back-a-micro-frontend-in-30-seconds</guid>
      <pubDate>Thu, 24 Sep 2026 09:00:00 GMT</pubDate>
      <description>A bad release is live and the clock is running. Most teams need fifteen minutes to undo it, because the version is baked into the host build. It need not be.</description>
      <category>microfrontends</category>
    </item>
    <item>
      <title>Deterministic AI Agents in Mission-Critical Systems: Why Microfrontend Boundaries Matter</title>
      <link>https://opsburg.dev/blog/ai-agents-microfrontend-determinism</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/ai-agents-microfrontend-determinism</guid>
      <pubDate>Sun, 13 Sep 2026 10:17:57 GMT</pubDate>
      <description>Learn how microfrontend architecture creates natural safety boundaries for AI agents in production. Reduce blast radius, increase determinism, and deploy AI reliably.</description>

    </item>
    <item>
      <title>How to Ship Canary Releases for Microfrontends Without Losing Your Mind</title>
      <link>https://opsburg.dev/blog/how-to-ship-canary-releases-for-microfrontends-without-losing-your-mind</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/how-to-ship-canary-releases-for-microfrontends-without-losing-your-mind</guid>
      <pubDate>Fri, 04 Sep 2026 07:20:00 GMT</pubDate>
      <description>Canary releases for MFEs are complex. Learn how they work, why DIY is painful, and how to implement them safely—step by step.</description>

    </item>
    <item>
      <title>Federation Solved Composition. Nobody Solved Deployment Reliability</title>
      <link>https://opsburg.dev/blog/federation-vs-orchestration</link>
      <guid isPermaLink="true">https://opsburg.dev/blog/federation-vs-orchestration</guid>
      <pubDate>Wed, 26 Aug 2026 21:48:10 GMT</pubDate>
      <description>Why Module Federation doesn&apos;t solve deployment reliability. The gap every MFE team rebuilds: canary releases, rollback, and safe deployments. What&apos;s missing from your stack</description>
      <category>microfrontends</category>
    </item>
  </channel>
</rss>
