https://luth.io/tags/turso/ Recent content in Turso on Luther Monson Hugo en Tue, 15 Sep 2026 21:08:00 -0700 https://luth.io/blog/2026/09/clustered-sqlite-cdc-cluster-channel/ Tue, 15 Sep 2026 21:08:00 -0700 https://luth.io/blog/2026/09/clustered-sqlite-cdc-cluster-channel/ <p>By the end of <a href="https://luth.io/blog/2026/08/clustered-sqlite-adding-turso/">Part 2</a> ePHPm v0.7.0 ran exactly one SQLite engine in process. That was Turso, for single-node and clustered mode alike. The sidecar was gone. What I skipped over is how a replica actually gets the primary&rsquo;s writes, and what happens when the primary dies with data on it. That&rsquo;s this post.</p> <ul> <li><a href="https://luth.io/blog/2026/08/clustered-sqlite-sqld-sidecar/">Part 1: Replication by sidecar with sqld</a></li> <li><a href="https://luth.io/blog/2026/08/clustered-sqlite-adding-turso/">Part 2: Adding Turso</a></li> <li>Part 3: CDC over the cluster channel (this post)</li> </ul> <h3 id="cdc-from-the-engine-itself">CDC from the engine itself</h3> <p>Turso has change data capture built in. Turn it on for a connection and every committed change lands in a <code>turso_cdc</code> table. Each row has a monotonically increasing <code>change_id</code>, the table, the rowid, and before/after images of the record. The primary tails that table and ships transaction batches. Replicas apply them. That&rsquo;s the whole design. It landed as an experimental path in <a href="https://github.com/ephpm/ephpm/pull/186">#186</a> at the end of July. The tailer and applier live in litewire (<a href="https://github.com/ephpm/litewire/pull/10">litewire#10</a>).</p> https://luth.io/blog/2026/08/what-does-one-more-wordpress-site-cost/ Tue, 25 Aug 2026 20:20:00 -0700 https://luth.io/blog/2026/08/what-does-one-more-wordpress-site-cost/ <p>ePHPm v0.7.0 shipped per-site multi-tenancy. Point <code>[server] sites_dir</code> at a directory and every <code>Host</code> maps to its own docroot and its own Turso database file. One process serves all of them. The first question anybody asks about that is &ldquo;how many sites fit on a box?&rdquo; The honest way to answer it is to turn the question around. What does <strong>one more</strong> site cost? If you know the marginal RAM, file descriptors, CPU and disk for a tenant, the box size falls out of arithmetic.</p> https://luth.io/blog/2026/08/clustered-sqlite-adding-turso/ Wed, 19 Aug 2026 20:37:00 -0700 https://luth.io/blog/2026/08/clustered-sqlite-adding-turso/ <p><a href="https://luth.io/blog/2026/08/clustered-sqlite-sqld-sidecar/">Part 1</a> ended with ePHPm running two SQLite engines. rusqlite ran in-process for a single node, and an embedded sqld child process ran for a cluster. The sidecar fell off a cliff past four concurrent writers. The best fix I could ship was a semaphore set to 1. This post is about replacing both engines with one, and about how I decided that engine was ready.</p> <ul> <li><a href="https://luth.io/blog/2026/08/clustered-sqlite-sqld-sidecar/">Part 1: Replication by sidecar with sqld</a></li> <li>Part 2: Adding Turso (this post)</li> <li><a href="https://luth.io/blog/2026/09/clustered-sqlite-cdc-cluster-channel/">Part 3: CDC over the cluster channel</a></li> </ul> <h3 id="the-thesis">The thesis</h3> <p><a href="https://github.com/tursodatabase/turso">Turso Database</a> is a rewrite of SQLite in Rust:</p>