<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Architecture &amp; Design - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Architecture &amp; Design Articles feed</description>
    <item>
      <title>Article: Architectural Change Cases: a Practical Tool for Evolutionary Architectures</title>
      <link>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/architectural-change-cases/en/headerimage/architectural-change-cases-header-1780316814045.jpg"/&gt;&lt;p&gt;Architectural change cases extend architecture decision record (ADR) thinking by evaluating how decisions may evolve over time. Change cases expose hidden assumptions and help teams estimate the reversibility and cost of change.&lt;/p&gt; &lt;i&gt;By Pierre Pureur, Kurt Bittner&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Architecture Documentation</category>
      <category>Architecture Evaluation</category>
      <category>Architecture Decision Records</category>
      <category>Evolutionary Architecture</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 04 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/architectural-change-cases/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Pierre Pureur, Kurt Bittner</dc:creator>
      <dc:date>2026-06-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/architectural-change-cases/en</dc:identifier>
    </item>
    <item>
      <title>Article: Two Misconfigurations That Caused Spark OOM Failures on Kubernetes</title>
      <link>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/spark-oom-kubernetes-misconfigurations/en/headerimage/spark-oom-kubernetes-misconfigurations-header-1780044756757.jpg"/&gt;&lt;p&gt;After migrating Spark pipelines to Azure Kubernetes Service, two infrastructure settings interacted destructively: spark.kubernetes.local.dirs.tmpfs=true backed shuffle spill with RAM instead of disk, and a hard podAffinity rule forced all executors onto one node. Together, they caused repeated OOM kills invisible to standard diagnostics.&lt;/p&gt; &lt;i&gt;By Pranav Bhasker&lt;/i&gt;</description>
      <category>Apache Spark</category>
      <category>Cloud</category>
      <category>Kubernetes</category>
      <category>DevOps</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 03 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/spark-oom-kubernetes-misconfigurations/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Pranav Bhasker</dc:creator>
      <dc:date>2026-06-03T09:00:00Z</dc:date>
      <dc:identifier>/articles/spark-oom-kubernetes-misconfigurations/en</dc:identifier>
    </item>
    <item>
      <title>Article: Stragglers, Not Failures: How Adaptive Hedged Requests Reduce p99 Latency by 74 Percent</title>
      <link>https://www.infoq.com/articles/adaptive-hedged-requests-p99-latency/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/adaptive-hedged-requests-p99-latency/en/headerimage/adaptive-hedged-requests-p99-latency-header-1779785816730.jpg"/&gt;&lt;p&gt;In fan-out microservice architectures, slow-but-completing requests accumulate across services and drive p99 latency far higher than per-service metrics suggest. This article presents an adaptive hedging mechanism that uses DDSketch for real-time quantile estimation, windowed rotation to handle distribution drift, and a token-bucket budget to prevent load amplification.&lt;/p&gt; &lt;i&gt;By Prathamesh Bhope&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>Distributed Systems</category>
      <category>Cloud</category>
      <category>Performance</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 28 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/adaptive-hedged-requests-p99-latency/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Prathamesh Bhope</dc:creator>
      <dc:date>2026-05-28T09:00:00Z</dc:date>
      <dc:identifier>/articles/adaptive-hedged-requests-p99-latency/en</dc:identifier>
    </item>
  </channel>
</rss>
