Okay, but this is a database now.
Is there a reason the replication needs to be built-in?
Is there a reason the replication needs to be built-in?
* SQLite which I mostly see as an embeddable database for applications, used on a server.
* Single table with key-value pairs.
* Having the tool for replication be a quite young project that's in active development.They have a single table with KV pairs right now as an artifact of having used the "database with built-in replication which is tailor built for key-value storage" you complain that they're moving away from. The point of the blog post is that they're doing that in part to move away from the single table of KV pairs.
They're not "sharding".
This is common but incorrect view of SQLite. It's able to handle many server-side workloads, as long as you're aware of its limitations (and the Tailscale team certainly are).