<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sql-Engines on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sql-engines/</link>
    <description>Recent content in Sql-Engines on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sql-engines/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Data Processing Engines — Databend vs Apache DataFusion vs Apache Ballista</title>
      <link>https://www.pistack.xyz/posts/2026-05-14-self-hosted-data-processing-engines-databend-vs-datafusion-vs-ballista-guide/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-14-self-hosted-data-processing-engines-databend-vs-datafusion-vs-ballista-guide/</guid>
      <description>&lt;p&gt;In the modern data stack, choosing the right data processing engine is critical for running analytics, ETL pipelines, and ad-hoc queries at scale. Three open-source projects have emerged as leading choices for self-hosted data processing: &lt;strong&gt;Databend&lt;/strong&gt;, &lt;strong&gt;Apache DataFusion&lt;/strong&gt;, and &lt;strong&gt;Apache Ballista&lt;/strong&gt;. Each takes a fundamentally different approach — from a complete cloud data warehouse to an embeddable query engine to a distributed compute cluster.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
