<?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: Comprehension as an Architectural Characteristic: A System That Is Not Understood Cannot Evolve Safely</title>
      <link>https://www.infoq.com/articles/system-comprehension-evolutionary-architecture/?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/system-comprehension-evolutionary-architecture/en/headerimage/header-1786087830832.jpg"/&gt;&lt;p&gt;As AI commoditizes code output, system comprehension silently decays, creating cognitive debt that threatens safe architectural evolution. This article explores why human understanding must be treated as an essential architectural characteristic, offering actionable strategies, socio-technical metrics, and design checkpoints to preserve intent across modern engineering teams.&lt;/p&gt; &lt;i&gt;By Jacobus Meintjes, Narayana Rengaswamy, Paul Katsande, Sureshbabu Bikki&lt;/i&gt;</description>
      <category>Generative AI</category>
      <category>Architecture ICSAET</category>
      <category>Evolutionary Architecture</category>
      <category>InfoQ Certification Program</category>
      <category>Code Reviews</category>
      <category>Leadership</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>Culture &amp; Methods</category>
      <category>article</category>
      <pubDate>Mon, 10 Aug 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/system-comprehension-evolutionary-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Jacobus Meintjes, Narayana Rengaswamy, Paul Katsande, Sureshbabu Bikki</dc:creator>
      <dc:date>2026-08-10T11:00:00Z</dc:date>
      <dc:identifier>/articles/system-comprehension-evolutionary-architecture/en</dc:identifier>
    </item>
    <item>
      <title>Article: Enabling Evolutionary Architecture through the Preservation of Change Locality</title>
      <link>https://www.infoq.com/articles/evolutionary-architecture-change-locality/?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/evolutionary-architecture-change-locality/en/headerimage/evolutionary-architecture-change-locality-header-1785239081753.jpg"/&gt;&lt;p&gt;Why do simple features suddenly require cross-team negotiations? In this article, explore how boundary drift quietly destroys change locality and increases cognitive load across teams. Learn practical sociotechnical strategies - redistributing mechanics, exposing essential policy, and rehearsing exception paths - to restore domain boundaries and enable a truly evolutionary software architecture.&lt;/p&gt; &lt;i&gt;By Michael Fischer, Nicholas Lawrence, Monica Karekar&lt;/i&gt;</description>
      <category>Topology</category>
      <category>Architecture ICSAET</category>
      <category>Domain Driven Design</category>
      <category>Evolutionary Architecture</category>
      <category>InfoQ Certification Program</category>
      <category>Sociotechnical Architecture</category>
      <category>Leadership</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Mon, 03 Aug 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/evolutionary-architecture-change-locality/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Michael Fischer, Nicholas Lawrence, Monica Karekar</dc:creator>
      <dc:date>2026-08-03T11:00:00Z</dc:date>
      <dc:identifier>/articles/evolutionary-architecture-change-locality/en</dc:identifier>
    </item>
    <item>
      <title>Article: Virtual Threads after JDK 24: What Changed for Production Java</title>
      <link>https://www.infoq.com/articles/virtual-threads-after-jdk24/?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/virtual-threads-after-jdk24/en/headerimage/virtual-threads-after-jdk24-header-1785232507934.jpg"/&gt;&lt;p&gt;JDK 24 removed the monitor-related carrier-thread pinning that stalled Netflix and similar teams on Java 21. What has replaced it on JDK 25 LTS is downstream-resource saturation: the bottleneck moved and now demands explicit bounding in application code. This article maps the failure modes that surface after virtual-thread adoption and gives a practical sequence backed by a public benchmark.&lt;/p&gt; &lt;i&gt;By Sandeep Bharadwaj&lt;/i&gt;</description>
      <category>Structured Concurrency</category>
      <category>JDK 24</category>
      <category>Java</category>
      <category>Spring Boot</category>
      <category>Virtual Thread</category>
      <category>ThreadLocal</category>
      <category>Spring MVC</category>
      <category>Reactor</category>
      <category>Spring WebFlux</category>
      <category>JDK 25</category>
      <category>Scoped Values</category>
      <category>JDK 21</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 31 Jul 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/virtual-threads-after-jdk24/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture+%26+Design-articles</guid>
      <dc:creator>Sandeep Bharadwaj</dc:creator>
      <dc:date>2026-07-31T09:00:00Z</dc:date>
      <dc:identifier>/articles/virtual-threads-after-jdk24/en</dc:identifier>
    </item>
  </channel>
</rss>
