3 ms·
It depends on your access pattern, if every application is write heavy to the same data set, this won't work. If every application is light on writes and those
by KingOfCoders 4y ago
It depends on your access pattern, if every application is write heavy to the same data set, this won't work. If every application is light on writes and those are mostly local (like for many SaaS companies), this will work fine with the future Litestream that redirect writes to one db and then distributes the data (if you can live with slightly stale data). Also depends on the size of you company. Slack does 300k/s messages, this won't work :-)
- cromd 4y agoOh, maybe I am behind on this “future litestream” that “redirects writes”. I only knew of the ability to sync/backup/restore. Do you have a link to something discussing those other features?
- ankraft 4y agoIt doesn’t redirect writes but you can create read-only replicas: https://github.com/benbjohnson/litestream-read-replica-example https://github.com/benbjohnson/litestream-read-replica-examp...
- KingOfCoders 4y ago"adding feature" https://fly.io/blog/all-in-on-sqlite-litestream/ https://fly.io/blog/all-in-on-sqlite-litestream/ "The upcoming release of Litestream will let you live-replicate SQLite directly between databases, which means you can set up a write-leader database with distributed read replicas. Read replicas can catch writes and redirect them to the leader"
- andrewchambers 4y agoYou can already do this by using rqlite to redirect writes.