<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Event-driven architecture: limit the number of updates in MVP Articles</title>
    <link>https://community.databricks.com/t5/mvp-articles/event-driven-architecture-limit-the-number-of-updates/m-p/147179#M62</link>
    <description>&lt;P&gt;One of the key challenges is limiting the number of updates—especially when there are many consecutive inserts (e.g., from Zerobus). &lt;BR /&gt;The AT MOST EVERY option in Databricks pipeline objects helps batch frequent events into controlled updates, reducing unnecessary recomputation and cost. #databricks&lt;/P&gt;
&lt;P&gt;&lt;A href="https://databrickster.medium.com/databricks-news-2026-week-5-26-january-2026-to-1-february-2026-d05b274adafe" target="_blank"&gt;https://databrickster.medium.com/databricks-news-2026-week-5-26-january-2026-to-1-february-2026-d05b274adafe&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="atmost.png" style="width: 864px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/23691i9BB31A50AE84551C/image-size/large?v=v2&amp;amp;px=999" role="button" title="atmost.png" alt="atmost.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 06 Feb 2026 18:14:35 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2026-02-06T18:14:35Z</dc:date>
    <item>
      <title>Event-driven architecture: limit the number of updates</title>
      <link>https://community.databricks.com/t5/mvp-articles/event-driven-architecture-limit-the-number-of-updates/m-p/147179#M62</link>
      <description>&lt;P&gt;One of the key challenges is limiting the number of updates—especially when there are many consecutive inserts (e.g., from Zerobus). &lt;BR /&gt;The AT MOST EVERY option in Databricks pipeline objects helps batch frequent events into controlled updates, reducing unnecessary recomputation and cost. #databricks&lt;/P&gt;
&lt;P&gt;&lt;A href="https://databrickster.medium.com/databricks-news-2026-week-5-26-january-2026-to-1-february-2026-d05b274adafe" target="_blank"&gt;https://databrickster.medium.com/databricks-news-2026-week-5-26-january-2026-to-1-february-2026-d05b274adafe&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="atmost.png" style="width: 864px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/23691i9BB31A50AE84551C/image-size/large?v=v2&amp;amp;px=999" role="button" title="atmost.png" alt="atmost.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Feb 2026 18:14:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/mvp-articles/event-driven-architecture-limit-the-number-of-updates/m-p/147179#M62</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2026-02-06T18:14:35Z</dc:date>
    </item>
  </channel>
</rss>

