<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Query Optimizer on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/query-optimizer/</link><description>Recent content in Query Optimizer on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 20 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/query-optimizer/index.xml" rel="self" type="application/rss+xml"/><item><title>Inside Stoolap: Unpacking the Storage Engine and Query Pipeline</title><link>https://ai-blog.noorshomelab.dev/mastering-stoolap-2026/stoolap-architecture-storage-query/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-stoolap-2026/stoolap-architecture-storage-query/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome back, fellow data adventurers! In our previous chapter, we got Stoolap up and running, and even executed our first few SQL queries. We saw how it feels to have a powerful database embedded directly within our application. But how does Stoolap manage to be so fast, concurrent, and versatile, especially when compared to older embedded databases like SQLite?&lt;/p&gt;
&lt;p&gt;The secret lies beneath the surface, within its meticulously designed architecture. In this chapter, we&amp;rsquo;re going to pull back the curtain and peek inside Stoolap&amp;rsquo;s core components: its &lt;strong&gt;Storage Engine&lt;/strong&gt; and &lt;strong&gt;Query Execution Pipeline&lt;/strong&gt;. Understanding these will not only satisfy your curiosity but also empower you to design more efficient schemas, write better queries, and truly leverage Stoolap&amp;rsquo;s modern capabilities for both transactional (OLTP) and analytical (OLAP) workloads, along with its cutting-edge vector search.&lt;/p&gt;</description></item></channel></rss>