<?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>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=Architecture</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>Availability</category>
      <category>Performance</category>
      <category>Architecture</category>
      <category>Cloud</category>
      <category>Architecture &amp; Design</category>
      <category>Development</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=Architecture</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>Netflix Cuts Cassandra Read Latency from Seconds to Milliseconds with Dynamic Partition Splitting</title>
      <link>https://www.infoq.com/news/2026/07/netflix-cassandra-partition/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</link>
      <description>&lt;img src="https://www.infoq.com/styles/static/images/logo/logo_bigger.jpg"/&gt;&lt;p&gt;Netflix engineers introduced dynamic partition splitting for Cassandra to address wide partitions in time series workloads. The metadata-driven approach detects oversized partitions, splits them smaller units, and routes reads across child partitions. Netflix reported lower read latency from seconds to milliseconds, reduced timeouts, and improved cluster stability while maintaining transparency.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Cassandra</category>
      <category>Partitioning</category>
      <category>Scalability</category>
      <category>Clusters</category>
      <category>Routing</category>
      <category>Low Latency</category>
      <category>Architecture</category>
      <category>Distributed Systems</category>
      <category>Metadata</category>
      <category>Time Series Data</category>
      <category>Data Partitioning</category>
      <category>Database</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 06 Jul 2026 14:24:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/07/netflix-cassandra-partition/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-07-06T14:24:00Z</dc:date>
      <dc:identifier>/news/2026/07/netflix-cassandra-partition/en</dc:identifier>
    </item>
    <item>
      <title>Mini book: Agentic AI Architecture</title>
      <link>https://www.infoq.com/minibooks/agentic-ai-architecture/?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/minibooks/agentic-ai-architecture/en/smallimage/agentic-ai-architecture-thumb-image-1782836155225.jpg"/&gt;&lt;p&gt;In this eMag, we try to establish agentic AI architecture as a new type of software architecture that will likely dominate the industry for years to come. The articles, written by industry experts, cover various elements and aspects of agentic AI architecture. We aim to present the latest trends and developments shaping the new type of architecture as it enters the mainstream.&lt;/p&gt; &lt;i&gt;By InfoQ&lt;/i&gt;</description>
      <category>Agents</category>
      <category>AI Architecture</category>
      <category>Frameworks</category>
      <category>Microservices</category>
      <category>Architecture &amp; Design</category>
      <category>minibook</category>
      <pubDate>Fri, 03 Jul 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/minibooks/agentic-ai-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>InfoQ</dc:creator>
      <dc:date>2026-07-03T11:00:00Z</dc:date>
      <dc:identifier>/minibooks/agentic-ai-architecture/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Enhancing Reliability Using Service-Level Prioritized Load Shedding at Netflix</title>
      <link>https://www.infoq.com/presentations/service-level-prioritized-load-shedding/?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/service-level-prioritized-load-shedding/en/mediumimage/medium-1782221254342.jpg"/&gt;&lt;p&gt;The speakers discuss Netflix’s architecture for surviving extreme traffic spikes. They explain the mechanics of prioritized load shedding embedded in their Envoy sidecar proxy, allowing user-initiated requests to steal capacity from non-critical traffic. They share automated platform strategies for continuous chaos load testing, config generation, and retry storm mitigation.&lt;/p&gt; &lt;i&gt;By Anirudh Mendiratta, Benjamin Fedorka&lt;/i&gt;</description>
      <category>Transcripts</category>
      <category>Platform Engineering</category>
      <category>Resilience</category>
      <category>QCon San Francisco 2025</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Thu, 02 Jul 2026 09:20:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/service-level-prioritized-load-shedding/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Anirudh Mendiratta, Benjamin Fedorka</dc:creator>
      <dc:date>2026-07-02T09:20:00Z</dc:date>
      <dc:identifier>/presentations/service-level-prioritized-load-shedding/en</dc:identifier>
    </item>
    <item>
      <title>Article: Scaling Java-Based Real-Time Systems: the Hidden Tradeoffs of Event-Driven Design</title>
      <link>https://www.infoq.com/articles/tradeoffs-event-driven-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/articles/tradeoffs-event-driven-design/en/headerimage/tradeoffs-event-driven-design-header-1782458803116.jpg"/&gt;&lt;p&gt;Event-driven architecture promises scalability, but in Java-based real-time systems the tradeoffs only surface in production. Drawing on a Java/Kafka contact center platform handling 80k BHCC across 10k agents, this article details where the design breaks down—state management, partition limits, deduplication, JVM tuning, cascading consumer failures—and the Redis-backed patterns that fixed each.&lt;/p&gt; &lt;i&gt;By Sagar Deepak Joshi&lt;/i&gt;</description>
      <category>Apache Kafka</category>
      <category>Java</category>
      <category>Spring Boot</category>
      <category>Redis</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Tue, 30 Jun 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/tradeoffs-event-driven-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Architecture</guid>
      <dc:creator>Sagar Deepak Joshi</dc:creator>
      <dc:date>2026-06-30T09:00:00Z</dc:date>
      <dc:identifier>/articles/tradeoffs-event-driven-design/en</dc:identifier>
    </item>
  </channel>
</rss>
