<?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 5 Reasons You Should Be Using LakeFlow Jobs as Your Default Orchestrator in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default/m-p/142717#M911</link>
    <description>&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;I recently saw a business case in which an external orchestrator accounted for nearly 30% of their total Databricks job costs. That's when it hit me: we're often paying a premium for complexity we don't need. Besides FinOps, I tried to gather all the reasons on my blogs for why Lakeflow should be your primary orchestrator.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;Read more:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;A href="https://databrickster.medium.com/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default-orchestrator-eb3a3389da19" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;https://databrickster.medium.com/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default-orchestrator-eb3a3389da19&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;A href="https://www.sunnydata.ai/blog/lakeflow-jobs-default-databricks-orchestrator" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;https://www.sunnydata.ai/blog/lakeflow-jobs-default-databricks-orchestrator&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="5reasons.png" style="width: 759px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/22586i801AB6007BE3D287/image-size/large?v=v2&amp;amp;px=999" role="button" title="5reasons.png" alt="5reasons.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 30 Dec 2025 19:48:42 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2025-12-30T19:48:42Z</dc:date>
    <item>
      <title>5 Reasons You Should Be Using LakeFlow Jobs as Your Default Orchestrator</title>
      <link>https://community.databricks.com/t5/community-articles/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default/m-p/142717#M911</link>
      <description>&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;I recently saw a business case in which an external orchestrator accounted for nearly 30% of their total Databricks job costs. That's when it hit me: we're often paying a premium for complexity we don't need. Besides FinOps, I tried to gather all the reasons on my blogs for why Lakeflow should be your primary orchestrator.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;Read more:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;A href="https://databrickster.medium.com/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default-orchestrator-eb3a3389da19" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;https://databrickster.medium.com/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default-orchestrator-eb3a3389da19&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;A href="https://www.sunnydata.ai/blog/lakeflow-jobs-default-databricks-orchestrator" target="_blank" rel="noopener"&gt;&lt;SPAN&gt;https://www.sunnydata.ai/blog/lakeflow-jobs-default-databricks-orchestrator&lt;/SPAN&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P class="first:mt-0 last:mb-0"&gt;&lt;SPAN&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="5reasons.png" style="width: 759px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/22586i801AB6007BE3D287/image-size/large?v=v2&amp;amp;px=999" role="button" title="5reasons.png" alt="5reasons.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 Dec 2025 19:48:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/5-reasons-you-should-be-using-lakeflow-jobs-as-your-default/m-p/142717#M911</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2025-12-30T19:48:42Z</dc:date>
    </item>
  </channel>
</rss>

