<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Infrastructure</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Infrastructure feed</description>
    <item>
      <title>Article: Time-Series Storage: Design Choices That Shape Cost and Performance</title>
      <link>https://www.infoq.com/articles/time-series-storage-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</link>
      <description>&lt;img src="https://res.infoq.com/articles/time-series-storage-design/en/headerimage/Time-Series-Storage-Design-Choices-That-Shape-Cost-and-Performance-header-1778155792101.jpg"/&gt;&lt;p&gt;Every time-series database makes a set of storage design decisions: how to lay out rows, when to compress, what to partition on. These decisions determine cost and query performance more than the choice of database itself. This article works through those fundamentals from first principles, using widely available tools like PostgreSQL and Apache Parquet to make each trade-off measurable.&lt;/p&gt; &lt;i&gt;By Nirmesh Khandelwal&lt;/i&gt;</description>
      <category>Big Data</category>
      <category>Time Series Data</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>article</category>
      <pubDate>Tue, 12 May 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/time-series-storage-design/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</guid>
      <dc:creator>Nirmesh Khandelwal</dc:creator>
      <dc:date>2026-05-12T09:00:00Z</dc:date>
      <dc:identifier>/articles/time-series-storage-design/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: Evolution of a Backend for a Streaming Application</title>
      <link>https://www.infoq.com/presentations/streaming-application-aws-infrastructure/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</link>
      <description>&lt;img src="https://res.infoq.com/presentations/streaming-application-aws-infrastructure/en/mediumimage/medium-1778061840987.jpg"/&gt;&lt;p&gt;Daniele Frasca explains the architectural evolution of Joyn, a German streaming giant. He discusses moving from fragile single-node setups to resilient serverless architectures using AWS. He shares insights on the Hub and Spoke pattern for data consistency, cell-based isolation to reduce blast radius, and cost-optimization strategies for achieving affordable multi-region active-active setups.&lt;/p&gt; &lt;i&gt;By Daniele Frasca&lt;/i&gt;</description>
      <category>Case Study</category>
      <category>AWS</category>
      <category>Transcripts</category>
      <category>Cloud</category>
      <category>Infrastructure</category>
      <category>InfoQ Dev Summit Munich 2025</category>
      <category>DevOps</category>
      <category>Architecture &amp; Design</category>
      <category>presentation</category>
      <pubDate>Mon, 11 May 2026 11:45:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/streaming-application-aws-infrastructure/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</guid>
      <dc:creator>Daniele Frasca</dc:creator>
      <dc:date>2026-05-11T11:45:00Z</dc:date>
      <dc:identifier>/presentations/streaming-application-aws-infrastructure/en</dc:identifier>
    </item>
    <item>
      <title>Presentation: How Netflix Shapes our Fleet for Efficiency and Reliability</title>
      <link>https://www.infoq.com/presentations/strategy-workload-hardware/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</link>
      <description>&lt;img src="https://res.infoq.com/presentations/strategy-workload-hardware/en/mediumimage/medium-1777370214319.jpg"/&gt;&lt;p&gt;The speakers explain the inherent tension between service efficiency and reliability at Netflix's global scale. They share a mental model for "risk-adjusted net value," moving beyond simple CPU utilization to focus on capacity buffers. They discuss hardware shaping, proactive traffic steering, and reactive levers like "hammers" and prioritized load shedding to protect critical playback.&lt;/p&gt; &lt;i&gt;By Joseph Lynch, Argha C&lt;/i&gt;</description>
      <category>Case Study</category>
      <category>Transcripts</category>
      <category>Resilience</category>
      <category>Hardware</category>
      <category>QCon San Francisco 2025</category>
      <category>DevOps</category>
      <category>presentation</category>
      <pubDate>Tue, 05 May 2026 14:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/presentations/strategy-workload-hardware/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</guid>
      <dc:creator>Joseph Lynch, Argha C</dc:creator>
      <dc:date>2026-05-05T14:00:00Z</dc:date>
      <dc:identifier>/presentations/strategy-workload-hardware/en</dc:identifier>
    </item>
    <item>
      <title>Article: From Batch to Micro-Batch Streaming: Lessons Learned the Hard Way in a Delta Index Pipeline</title>
      <link>https://www.infoq.com/articles/micro-batch-streaming-lessons-learned/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</link>
      <description>&lt;img src="https://res.infoq.com/articles/micro-batch-streaming-lessons-learned/en/headerimage/micro-batch-streaming-lessons-learned-header-1777381781538.jpg"/&gt;&lt;p&gt;This article describes how a production delta-index pipeline migrated from scheduled batch to micro-batch Spark Structured Streaming. It covers why record-level streaming was rejected, how partition-based watermarks replaced fragile S3 completion markers,  overlap-window correctness, and restart-as-design strategies for better predictability in object-store–based ingestion systems.&lt;/p&gt; &lt;i&gt;By Parveen Saini&lt;/i&gt;</description>
      <category>Spark Streaming</category>
      <category>Apache Spark</category>
      <category>AI, ML &amp; Data Engineering</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Mon, 04 May 2026 11:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/micro-batch-streaming-lessons-learned/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Infrastructure</guid>
      <dc:creator>Parveen Saini</dc:creator>
      <dc:date>2026-05-04T11:00:00Z</dc:date>
      <dc:identifier>/articles/micro-batch-streaming-lessons-learned/en</dc:identifier>
    </item>
  </channel>
</rss>
