<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Architecture</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Architecture feed</description>
    <item>
      <title>Applying Best Simple System for Now for Software Design</title>
      <link>https://www.infoq.com/news/2026/05/best-simple-system-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/05/best-simple-system-design/en/headerimage/best-simple-system-design-header-1776687343321.jpg"/&gt;&lt;p&gt;Choosing between building up technical debt and missing delivery deadlines is a false dichotomy, Daniel Terhorst-North argued in his talk Best Simple System for Now. Programmers love to generalize rather than solve the immediate problem at hand, which can make future changes difficult. Instead, we need to build the skills and instincts for keeping things simple.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>Design</category>
      <category>GOTO Conference</category>
      <category>Scalability</category>
      <category>Technical Debt</category>
      <category>Code Quality</category>
      <category>Culture &amp; Methods</category>
      <category>news</category>
      <pubDate>Thu, 07 May 2026 11:43:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/05/best-simple-system-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-05-07T11:43:00Z</dc:date>
      <dc:identifier>/news/2026/05/best-simple-system-design/en</dc:identifier>
    </item>
    <item>
      <title>Article: Beyond the Benchmark: a Metrics-Driven Approach to Sustained iOS Performance on Real Devices</title>
      <link>https://www.infoq.com/articles/metrics-driven-approach-ios-performance/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</link>
      <description>&lt;img src="https://res.infoq.com/articles/metrics-driven-approach-ios-performance/en/headerimage/metrics-driven-approach-ios-performance-header-1777624958302.jpg"/&gt;&lt;p&gt;iOS performance engineering often defaults to a mental model where performance is a property of a component. Performance is instead an emergent behavior of the interaction between application code, device hardware, OS resource management, network conditions, and user behavior patterns over time. This article gives a direct, first-party path to capturing performance issues using Xcode Instruments.&lt;/p&gt; &lt;i&gt;By Vasuki Uday Kiran Vudathala&lt;/i&gt;</description>
      <category>Performance</category>
      <category>User Experience</category>
      <category>iOS</category>
      <category>Xcode</category>
      <category>Mobile</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Wed, 06 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/metrics-driven-approach-ios-performance/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Vasuki Uday Kiran Vudathala</dc:creator>
      <dc:date>2026-05-06T09:00:00Z</dc:date>
      <dc:identifier>/articles/metrics-driven-approach-ios-performance/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: How Netflix Shapes our Fleet for Efficiency and Reliability</title>
      <link>https://www.infoq.com/presentations/strategy-workload-hardware/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</link>
      <description>&lt;img src="https://res.infoq.com/presentations/strategy-workload-hardware/en/mediumimage/medium-1777370214319.jpg"/&gt;&lt;p&gt;The speakers explain the inherent tension between service efficiency and reliability at Netflix's global scale. They share a mental model for "risk-adjusted net value," moving beyond simple CPU utilization to focus on capacity buffers. They discuss hardware shaping, proactive traffic steering, and reactive levers like "hammers" and prioritized load shedding to protect critical playback.&lt;/p&gt; &lt;i&gt;By Joseph Lynch, Argha C&lt;/i&gt;</description>
      <category>Case Study</category>
      <category>Transcripts</category>
      <category>Resilience</category>
      <category>Hardware</category>
      <category>QCon San Francisco 2025</category>
      <category>DevOps</category>
      <category>presentation</category>
      <pubDate>Tue, 05 May 2026 14:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/strategy-workload-hardware/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Joseph Lynch, Argha C</dc:creator>
      <dc:date>2026-05-05T14:00:00Z</dc:date>
      <dc:identifier>/presentations/strategy-workload-hardware/en</dc:identifier>
    </item>
    <item>
      <title>Article: Three Pillars of Platform Engineering: a Virtuous Cycle</title>
      <link>https://www.infoq.com/articles/platform-reliability-cycle/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</link>
      <description>&lt;img src="https://res.infoq.com/articles/platform-reliability-cycle/en/headerimage/platform-reliability-cycle-header-1777467114542.jpg"/&gt;&lt;p&gt;Platform engineering succeeds when reliability and ergonomics reinforce each other rather than compete. This article explores three foundational pillars: automated reliability, developer ergonomics, and operator ergonomics. Together, they establish a virtuous cycle that strengthens system stability, reduces operational burden, and empowers teams to scale infrastructure with confidence.&lt;/p&gt; &lt;i&gt;By Pratik Agarwal&lt;/i&gt;</description>
      <category>Distributed Systems</category>
      <category>Observability</category>
      <category>Platform Engineering</category>
      <category>Developer Experience</category>
      <category>Site Reliability Engineering</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 05 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/platform-reliability-cycle/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Pratik Agarwal</dc:creator>
      <dc:date>2026-05-05T09:00:00Z</dc:date>
      <dc:identifier>/articles/platform-reliability-cycle/en</dc:identifier>
    </item>
  </channel>
</rss>
