https://appcoding.com/tags/embedded-databases/ Recent content in Embedded Databases on App Coding Hugo en-us Fri, 09 Oct 2026 00:00:00 +0000 https://appcoding.com/40-projects-worth-building-sqlite-for-x-tiny-infrastructure-mcp-tools-and-edge-systems/ Fri, 09 Oct 2026 00:00:00 +0000 https://appcoding.com/40-projects-worth-building-sqlite-for-x-tiny-infrastructure-mcp-tools-and-edge-systems/ <p>The most promising territory for a small team isn&rsquo;t another large framework. It&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 <a href="https://appcoding.com/one-binary-one-file-no-daemon-the-sqlite-and-nginx-pattern-as-a-product-strategy/">the SQLite and nginx pattern as a product strategy</a>.)</p> https://appcoding.com/a-background-job-queue-in-one-sqlite-file-covers-what-most-apps-deploy-redis-for/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/a-background-job-queue-in-one-sqlite-file-covers-what-most-apps-deploy-redis-for/ <p>A signup handler has to send a welcome email, and sending it inline puts a third-party API call inside your request. So you move it into a background job, and the usual next step is Redis, a client library, a worker process, a dashboard, and a note in the deploy docs about what happens to queued jobs when Redis restarts without persistence. If the app runs on one machine, you&rsquo;ve added a second stateful service to look after a table&rsquo;s worth of data.</p> https://appcoding.com/a-feature-store-small-enough-to-embed-point-in-time-reads-for-local-and-edge-ml/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/a-feature-store-small-enough-to-embed-point-in-time-reads-for-local-and-edge-ml/ <p>A churn model looks excellent in the notebook and mediocre in production. The model isn&rsquo;t broken. The training table computed <code>orders_7d</code> with a rolling window over the full history, so some rows counted orders placed after the label date. The serving code, written later in another language, counts a calendar week instead of seven days. One feature, two definitions, and a quiet look into the future. Those are the two bugs a feature store exists to prevent: training-serving skew and label leakage.</p> https://appcoding.com/embedded-vector-search-is-crowded-what-a-one-file-vector-database-needs-to-stand-out/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/embedded-vector-search-is-crowded-what-a-one-file-vector-database-needs-to-stand-out/ <p>You have 40,000 support articles and an app that should offer &ldquo;similar articles&rdquo;. Embedded at 768 dimensions in float32, that&rsquo;s 40,000 × 768 × 4 bytes, about 123 MB of vectors. The standard advice is to stand up a vector database: a service, a port, credentials, a client library and a backup story for 123 MB. A file would do.</p> <p>Below a few million vectors the server is the overhead, which is why the embedded field filled up fast. So the useful question is what a newcomer brings that the free libraries don&rsquo;t. My answer is one sharp edge you can state in a sentence, plus measurements the others leave you to make yourself.</p> https://appcoding.com/kafka-for-one-machine-an-embedded-event-log-with-offsets-compaction-and-no-broker/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/kafka-for-one-machine-an-embedded-event-log-with-offsets-compaction-and-no-broker/ <p>A desktop app wants an undo history that survives a crash. An edge gateway buffers sensor readings while its uplink is down and has to replay them, in order, once the link is back. An AI agent writes down every action it takes so a bad run can be replayed later. All three are the same data structure: an append-only sequence of records, plus readers that remember where they stopped. Kafka is that structure, and also a cluster, partitions and the people who tune them.</p> https://appcoding.com/redis-semantics-without-redis-an-embedded-state-engine-for-counters-leases-and-ttls/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/redis-semantics-without-redis-an-embedded-state-engine-for-counters-leases-and-ttls/ <p>A command-line tool should run only one copy of its nightly export at a time. A small web app wants to cap each user at 60 requests a minute. A desktop app needs to remember when it last synced. All three are state: an integer, a timestamp, an owner. All three usually get solved by adding Redis, because Redis has the verbs for them: <code>INCR</code>, <code>SET NX PX</code>, <code>EXPIRE</code>. The app needed the verbs and got a server along with them, a port and a persistence config included.</p> https://appcoding.com/sql-and-key-value-over-the-same-bytes-an-old-database-idea-worth-making-small/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/sql-and-key-value-over-the-same-bytes-an-old-database-idea-worth-making-small/ <p>A sensor node writes a reading every few seconds. The firmware wants one thing from storage: put a record by key, get it back by key, as fast as the flash allows. The dashboard on the gateway wants something else, like average temperature by sensor by hour, joined to a table of sites. The usual answer is two databases with a translation job between them, a key-value store on the device and SQLite or Postgres upstream. Then comes a year of debugging the translation: a unit that changed, a row that arrived twice, a field the device encodes one way and the gateway reads another.</p> https://appcoding.com/store-changes-instead-of-current-rows-an-embedded-database-built-around-history/ Mon, 05 Oct 2026 00:00:00 +0000 https://appcoding.com/store-changes-instead-of-current-rows-an-embedded-database-built-around-history/ <p>A support ticket asks two plain questions: which plan was customer 4411 on when the August invoice went out, and who moved them off it? The <code>customers</code> table can&rsquo;t answer either. It holds today&rsquo;s row. The audit table someone added two years ago holds most of the story, apart from the week a data fix ran a bulk <code>UPDATE</code> in raw SQL and skipped the ORM callbacks that write the audit rows.</p> https://appcoding.com/altsql-gives-iot-devices-a-15-kb-database-that-keeps-working-when-the-link-drops/ Fri, 02 Oct 2026 00:00:00 +0000 https://appcoding.com/altsql-gives-iot-devices-a-15-kb-database-that-keeps-working-when-the-link-drops/ <p>Anyone who has built the software side of a connected product knows the integration job. The device keeps its readings and settings in one format and the gateway or cloud service wants those same values as rows in a SQL database. Somebody writes a converter. Then somebody has to keep that converter alive for as long as the device stays in the field, which for industrial equipment or embedded systems can easily be ten years. The converter has to handle offline periods, retries, out-of-order updates, and the device&rsquo;s own data format changing over time.</p>