<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Partitioning</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Partitioning feed</description>
    <item>
      <title>Article: Distributed Spring Batch without a Message Broker</title>
      <link>https://www.infoq.com/articles/spring-batch-without-broker/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Partitioning</link>
      <description>&lt;img src="https://res.infoq.com/articles/spring-batch-without-broker/en/headerimage/Distributed-Spring-Batch-Without-a-Message-Broker-header-1792419294298.jpg"/&gt;&lt;p&gt;Distributed Spring Batch partitioning already needs a shared, persistent job repository. This article makes that database the whole coordination plane and drops the message broker, sizing work to the live node count, a per-job master with no standing coordinator, compare-and-set claiming that prevents double-execution, two-phase heartbeat failover, and where a broker is still the right choice.&lt;/p&gt; &lt;i&gt;By Janardhan Reddy Chejarla&lt;/i&gt;</description>
      <category>Data Partitioning</category>
      <category>Spring Batch</category>
      <category>Java</category>
      <category>Messaging</category>
      <category>Distributed Systems</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Wed, 21 Oct 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/spring-batch-without-broker/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Partitioning</guid>
      <dc:creator>Janardhan Reddy Chejarla</dc:creator>
      <dc:date>2026-10-21T09:00:00Z</dc:date>
      <dc:identifier>/articles/spring-batch-without-broker/en</dc:identifier>
    </item>
    <item>
      <title>Pinterest Uses Event Time Watermarks to Finalize Petabyte Scale Data Partitions</title>
      <link>https://www.infoq.com/news/2026/10/pinterest-event-time-partition/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Partitioning</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/10/pinterest-event-time-partition/en/headerimage/generatedHeaderImage-1791063877867.jpg"/&gt;&lt;p&gt;Pinterest has introduced event time-based partition finalization for its database ingestion framework. The mechanism uses Apache Flink to track event time and Apache Iceberg metadata to publish a non-regressing watermark, helping downstream jobs determine when continuously ingested CDC data is sufficiently complete for processing.&lt;/p&gt; &lt;i&gt;By Leela Kumili&lt;/i&gt;</description>
      <category>Change Data Capture</category>
      <category>Apache Kafka</category>
      <category>Data Partitioning</category>
      <category>Partitioning</category>
      <category>Data Lake</category>
      <category>Event Driven Architecture</category>
      <category>Apache Spark</category>
      <category>Streaming</category>
      <category>Apache Iceberg</category>
      <category>Apache Flink</category>
      <category>Distributed Systems</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Mon, 19 Oct 2026 14:37:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/10/pinterest-event-time-partition/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Partitioning</guid>
      <dc:creator>Leela Kumili</dc:creator>
      <dc:date>2026-10-19T14:37:00Z</dc:date>
      <dc:identifier>/news/2026/10/pinterest-event-time-partition/en</dc:identifier>
    </item>
  </channel>
</rss>
