etcd vs SQLite for a control plane: Tailscale's migration
Published 2026-10-19 · Built only from first-party engineering write-ups in our database. Every number below comes from the linked source.
Tailscale's post is the direct comparison: it replaced etcd with SQLite plus Litestream replication for a simpler control-plane datastore. SQLite shows up at scale elsewhere too: Cloudflare's D1 manages millions of SQLite databases at the edge, and Notion caches data in the browser with WASM SQLite.
etcd vs SQLite: side by side
| etcd | SQLite | |
|---|---|---|
| Stories in our database | 1 | 4 |
| Companies | Tailscale | Cloudflare, Discord, Notion and Tailscale |
| Published | 2022 | 2022–2026 |
| Techniques alongside it | database migration (1), replication (1), simplification (1) | client-side caching (1), control plane separation (1), database migration (1), database operations automation (1) |
| Scale numbers stated in sources | None stated | millions of databases (Cloudflare); dozens of clusters, hundreds of database nodes (Discord) |
| Direct comparison story | Tailscale: Switching from etcd to SQLite: A Database Migration Story | (same story) |
Verdict
Tailscale picked simplicity for one control-plane datastore. That's a different job from a multi-node consensus store, so read the post before copying the move.
Counts are stories in How They Scaled tagged with each side, see the SQLite pages. They describe what these teams wrote about, not market share or benchmark results.