<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Development - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Development 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=Development-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>Architecture Decision Records</category>
      <category>Evolutionary Architecture</category>
      <category>Architecture Evaluation</category>
      <category>Architecture Documentation</category>
      <category>Transcripts</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=Development-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=Development-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>Cloud</category>
      <category>Apache Spark</category>
      <category>Kubernetes</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>DevOps</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=Development-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: The AI Productivity Paradox in Test Automation: Moving Beyond Structural Validation to Perception and Intent</title>
      <link>https://www.infoq.com/articles/solving-ai-productivity-paradox-test-automation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/solving-ai-productivity-paradox-test-automation/en/headerimage/solving-ai-productivity-paradox-test-automation-header-1779953915743.jpg"/&gt;&lt;p&gt;The AI productivity paradox states that AI scales whatever abstraction it is built on. If that abstraction is structurally brittle, it scales structural brittleness. This article shows how, to build a future of reliable, AI-driven test automation, we must stop scaling DOM-centric abstractions and build a new testing paradigm grounded in perception and intent.&lt;/p&gt; &lt;i&gt;By Amanul Chowdhury, Vinay Gummadavelli&lt;/i&gt;</description>
      <category>Web Development</category>
      <category>JavaScript</category>
      <category>Large language models</category>
      <category>Test Automation</category>
      <category>HTML</category>
      <category>UI Testing</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Mon, 01 Jun 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/solving-ai-productivity-paradox-test-automation/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Amanul Chowdhury, Vinay Gummadavelli</dc:creator>
      <dc:date>2026-06-01T11:00:00Z</dc:date>
      <dc:identifier>/articles/solving-ai-productivity-paradox-test-automation/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=Development-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>Cloud</category>
      <category>Architecture</category>
      <category>Distributed Systems</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=Development-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>
    <item>
      <title>Article: Architecting Cloud-Native Kafka: from Tiered Storage towards a Diskless Future</title>
      <link>https://www.infoq.com/articles/architecting-cloud-native-kafka/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/architecting-cloud-native-kafka/en/headerimage/architecting-cloud-native-kafka-header-1779433382367.jpg"/&gt;&lt;p&gt;This article explores Kafka's transition toward a cloud-native architecture, examining how tiered storage, FinOps telemetry, elastic consumer scaling, virtual clusters, and Share Groups reshape the operational and economic model of event streaming platforms. It also analyzes emerging diskless-storage proposals and their architectural trade-offs.&lt;/p&gt; &lt;i&gt;By Viquar Khan&lt;/i&gt;</description>
      <category>Kafka Streams</category>
      <category>Apache Kafka</category>
      <category>Cloud-Native</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 26 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/architecting-cloud-native-kafka/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Viquar Khan</dc:creator>
      <dc:date>2026-05-26T09:00:00Z</dc:date>
      <dc:identifier>/articles/architecting-cloud-native-kafka/en</dc:identifier>
    </item>
    <item>
      <title>Article: The Schema Proliferation Problem in Kafka and Flink Pipelines: How to Solve It</title>
      <link>https://www.infoq.com/articles/schema-proliferation-problem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/schema-proliferation-problem/en/headerimage/schema-proliferation-problem-header-1779270222602.jpg"/&gt;&lt;p&gt;Schema proliferation builds slowly and gets expensive fast. One schema per event type feels right until there are ten tables, union queries spanning all of them, and a single field rename touching every schema. Discriminator-based schema consolidation collapses that to two tables, turning multi-table unions into a single query, while new variants are additive and don't break existing consumers.&lt;/p&gt; &lt;i&gt;By Spoorthi Basu&lt;/i&gt;</description>
      <category>Schema</category>
      <category>Apache Iceberg</category>
      <category>Apache Flink</category>
      <category>Apache Kafka</category>
      <category>Java</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 25 May 2026 13:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/schema-proliferation-problem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Spoorthi Basu</dc:creator>
      <dc:date>2026-05-25T13:00:00Z</dc:date>
      <dc:identifier>/articles/schema-proliferation-problem/en</dc:identifier>
    </item>
  </channel>
</rss>
