I thought litestream was just for streaming backups? How does it enable you to coordinate with multiple instances of an application? Is one instance the "primary" where writes all go and either can serve as a reader?
The other instances are mostly redundant. That's how sites like Hacker News tend to operate, and why I chose this architecture. It's simple and stupid but doesn't work in scenarios where you have multiple servers in different locations for example. There's LiteFS to solve this problem but I don't have experience with it yet.
Cheers
How litestream handles master-master or promoting a slave and switching back later isn't clear to me.
https://joshkaramuth.com/blog/django-deployment/
But it doesn't go over multi-instance coordination