<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Micro-Frontends on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/micro-frontends/</link>
    <description>Recent content in Micro-Frontends on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/micro-frontends/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Module Federation vs single-spa vs qiankun in 2026: Which Micro-Frontend Architecture Survives Production?</title>
      <link>https://www.pistack.xyz/posts/2026-10-21-micro-frontends-module-federation-single-spa-qiankun/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-21-micro-frontends-module-federation-single-spa-qiankun/</guid>
      <description>&lt;p&gt;The pitch for micro-frontends is always the same: forty engineers, one React app, six teams blocked on the same release train. Split the frontend, let each team deploy independently, ship faster. Then eighteen months later the shell takes nine seconds to load, two copies of React are running, a CSS reset from the checkout app is repainting the navbar, and nobody can explain why the payment button works in staging but not in production.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
