<?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: Comprehension at AI Speed: Building a Context Store for Evolutionary Architecture</title>
      <link>https://www.infoq.com/articles/ai-speed-context-store-architecture/?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/ai-speed-context-store-architecture/en/headerimage/ai-speed-context-store-architecture-header-1783673492911.jpg"/&gt;&lt;p&gt;AI makes the first 80% of development feel fast, but hides architectural complexity until it's too late. To prevent system instability, engineering leaders must shift from raw throughput to systemic comprehension. By unifying spec-anchored SDD, TDD, and automated fitness functions into a repo-bound "Context Store," teams can ensure AI agents and human reviewers evolve code safely.&lt;/p&gt; &lt;i&gt;By Stella Berhe, Stephan Bragner, Vikram Maran, Anand Jayaraman&lt;/i&gt;</description>
      <category>Specification</category>
      <category>Architecture ICSAET</category>
      <category>Evolutionary Architecture</category>
      <category>InfoQ Certification Program</category>
      <category>TDD</category>
      <category>Artificial Intelligence</category>
      <category>Governance</category>
      <category>AI Development</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Tue, 14 Jul 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/ai-speed-context-store-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Stella Berhe, Stephan Bragner, Vikram Maran, Anand Jayaraman</dc:creator>
      <dc:date>2026-07-14T09:00:00Z</dc:date>
      <dc:identifier>/articles/ai-speed-context-store-architecture/en</dc:identifier>
    </item>
    <item>
      <title>Article: Removing a Hidden Round Trip from a Multi-Region AWS API</title>
      <link>https://www.infoq.com/articles/aws-multi-region-signing/?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/aws-multi-region-signing/en/headerimage/aws-multi-region-signing-header-1783602485181.jpg"/&gt;&lt;p&gt;When a series of regional outages forced a rethink of a multi-region AWS API, the team discovered that an obstacle to global failover was hiding in plain sight: a pre-flight discovery call baked into every client session years earlier as the only available option. This article describes what it took to remove it, and what the rollout actually cost.&lt;/p&gt; &lt;i&gt;By Suresh Gururajan&lt;/i&gt;</description>
      <category>Low Latency</category>
      <category>AWS</category>
      <category>multi-region</category>
      <category>Cloud</category>
      <category>Resilience</category>
      <category>Authentication</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Mon, 13 Jul 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/aws-multi-region-signing/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Suresh Gururajan</dc:creator>
      <dc:date>2026-07-13T11:00:00Z</dc:date>
      <dc:identifier>/articles/aws-multi-region-signing/en</dc:identifier>
    </item>
    <item>
      <title>Article: Trade-Offs in Multi-Region Architectures: Latency vs. Cost</title>
      <link>https://www.infoq.com/articles/multi-region-latency-cost-tradeoffs/?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/multi-region-latency-cost-tradeoffs/en/headerimage/multi-region-latency-cost-tradeoffs-header-1783416229477.jpg"/&gt;&lt;p&gt;Adding cloud regions changes latency and cost in ways simple math can't capture. This article presents a framework from multiple launches: decompose your latency budget before committing to infrastructure, choose deployment patterns by consistency and traffic profile, and optimize before expanding. A phased approach cut latency 35% through routing alone, before a new region brought it under 60ms.&lt;/p&gt; &lt;i&gt;By Uttara Asthana&lt;/i&gt;</description>
      <category>Architecture</category>
      <category>Cloud</category>
      <category>Availability</category>
      <category>Performance</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>DevOps</category>
      <category>article</category>
      <pubDate>Fri, 10 Jul 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/multi-region-latency-cost-tradeoffs/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Uttara Asthana</dc:creator>
      <dc:date>2026-07-10T09:00:00Z</dc:date>
      <dc:identifier>/articles/multi-region-latency-cost-tradeoffs/en</dc:identifier>
    </item>
    <item>
      <title>Article: Beat-Aligned Mobile Audio Streaming with Virtual Chunks and Native Playback</title>
      <link>https://www.infoq.com/articles/android-beat-aligned-mobile-audio-streaming/?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/android-beat-aligned-mobile-audio-streaming/en/headerimage/android-beat-aligned-mobile-audio-streaming-header-1783408153943.jpg"/&gt;&lt;p&gt;In this article, I describe the challenges and the design of a React Native real-time mobile beat-aligned playback system for iOS and Android. The system combines personalization with low-latency, and seamless navigation and was the result of careful analysis and experimentation to address strict mobile and network constraints as well as meet user expectations.&lt;/p&gt; &lt;i&gt;By Vladyslav Melnychenko&lt;/i&gt;</description>
      <category>React Native</category>
      <category>C++</category>
      <category>Real Time</category>
      <category>Android</category>
      <category>Mobile</category>
      <category>iOS</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 09 Jul 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/android-beat-aligned-mobile-audio-streaming/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Development-articles</guid>
      <dc:creator>Vladyslav Melnychenko</dc:creator>
      <dc:date>2026-07-09T09:00:00Z</dc:date>
      <dc:identifier>/articles/android-beat-aligned-mobile-audio-streaming/en</dc:identifier>
    </item>
  </channel>
</rss>
