Turso bets on per-agent SQLite databases, but the new sync engine is still in beta

从每个租户一库到每个 Agent 一库：Turso 的产品赌注与竞争版图

Turso started with edge SQLite to cut latency, then moved to per-tenant databases, and now pushes the boundary to per-agent or per-task databases. The pitch: libSQL branches plus AgentFS pack files, KV state, and audit logs into a single SQLite file that syncs to the cloud via explicit push/pull. The new Turso Database engine, Sync protocol, and AgentFS are all still in private beta or beta—the post warns not to confuse this with the mature Turso Cloud. Real trade-offs include schema migration across hundreds of thousands of databases and application-level conflict resolution during sync.

Why it matters: A solid deep-dive on Turso's product evolution toward per-agent databases, with concrete technical details and competitive landscape analysis. Held back from higher scores because it's a single-product analysis rather than an industry event, and the post doesn't disclose perfo...