<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="https://umn7fc98gj7rc.julianrbryant.com/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Distributed Systems - Presentations</title>
    <link>https://un5gmtkzgjn63apf3w.julianrbryant.com</link>
    <description>InfoQ Distributed Systems Presentations feed</description>
    <item>
      <title>Presentation: The Ideal Micro-Frontends Platform</title>
      <link>https://un5gmtkzgjn63apf3w.julianrbryant.com/presentations/distributed-micro-frontends/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-presentations</link>
      <description>&lt;img src="https://un5pmbagwnwm69a3.julianrbryant.com/presentations/distributed-micro-frontends/en/mediumimage/luca-mezzalira-medium-1769525111295.jpeg"/&gt;&lt;p&gt;Luca Mezzalira shares a decision framework for micro-frontends, covering composition, routing, and communication. He explains how to structure "stream-aligned" teams and use a "tiger team" for foundational architecture. He also discusses the sociotechnical benefits of reducing external dependencies and shares how to use guardrails and discovery services to achieve 25+ deployments per day.&lt;/p&gt; &lt;i&gt;By Luca Mezzalira&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Web Development</category>
      <category>Transcripts</category>
      <category>Front-end</category>
      <category>InfoQ Dev Summit Boston 2025</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Mon, 16 Feb 2026 15:45:00 GMT</pubDate>
      <guid>https://un5gmtkzgjn63apf3w.julianrbryant.com/presentations/distributed-micro-frontends/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Distributed+Systems-presentations</guid>
      <dc:creator>Luca Mezzalira</dc:creator>
      <dc:date>2026-02-16T15:45:00Z</dc:date>
      <dc:identifier>/presentations/distributed-micro-frontends/en</dc:identifier>
    </item>
  </channel>
</rss>
