I guess I’m missing something fundamental after listening to this talk, I have two servers that talk to the same database. As far as I can tell using SQLite in prod does not scale past a single server. Is there something here I didn’t understand?
That is true in itself, though offerings like Turso /LibSQL make it possible to have changes be synchronized between a central server and your web servers. Before Turso, I've deployed some applications that just redirected write traffic to a master server and used tools, like Litestream, to update the read replicas automatically. Using Sqlite with multiple databases and database files, one person tenant, made it possible to still distribute writes, since each server was the master of a few of those tenants. With tools like Turso the effort to implement such solutions goes down dramatically though
I guess I’m missing something fundamental after listening to this talk, I have two servers that talk to the same database. As far as I can tell using SQLite in prod does not scale past a single server. Is there something here I didn’t understand?
That is true in itself, though offerings like Turso /LibSQL make it possible to have changes be synchronized between a central server and your web servers.
Before Turso, I've deployed some applications that just redirected write traffic to a master server and used tools, like Litestream, to update the read replicas automatically.
Using Sqlite with multiple databases and database files, one person tenant, made it possible to still distribute writes, since each server was the master of a few of those tenants.
With tools like Turso the effort to implement such solutions goes down dramatically though
And now your vendor locked in to Turso when you could have just used Postgresql