<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Embedded Databases on App Coding</title>
    <link>https://appcoding.com/tags/embedded-databases/</link>
    <description>Recent content in Embedded Databases on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/embedded-databases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>40 Projects Worth Building: SQLite for X, Tiny Infrastructure, MCP Tools and Edge Systems</title>
      <link>https://appcoding.com/40-projects-worth-building-sqlite-for-x-tiny-infrastructure-mcp-tools-and-edge-systems/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/40-projects-worth-building-sqlite-for-x-tiny-infrastructure-mcp-tools-and-edge-systems/</guid>
      <description>&lt;p&gt;The most promising territory for a small team isn&amp;rsquo;t another large framework. It&amp;rsquo;s the opposite: infrastructure software you can explain in one sentence, ship as one binary or embed as one library, run with almost no operational burden, and that solves one irritating problem unusually well. SQLite and nginx are the right mental models because their appeal is architectural, not just functional: small surface area, predictable behavior, few dependencies, easy deployment, and usefulness far beyond the original use case. (More on that in &lt;a href=&#34;https://appcoding.com/one-binary-one-file-no-daemon-the-sqlite-and-nginx-pattern-as-a-product-strategy/&#34;&gt;the SQLite and nginx pattern as a product strategy&lt;/a&gt;.)&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
