Write Once - Read Many #311
-
I'm working on a project that I think Litestream would be great for. I have a daemon that is collecting data and writing to a SQLite database and RESTful API layer that allows reading (but not writing). If the number of readers needs to scale (questionable) I would want to
The straightforward way to do it is to just have the reader apps copy the entire db file over on a schedule. If I have a list of all the readers that are running, can I have a different Litestream instance watching the common storage DB and stream changes to the readers? Or is copying the full file over on a schedule "better"? Thanks! rjsjr |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
@wobbet I have live replication (#8) almost working. That'll let you have one writer node and multiple read-only nodes streaming changes in real-time. Is that what you're looking for? I'm hoping to have it finished and cleaned up by the end of the month and then spend most of March doing testing and performance improvements. It'll release with v0.4.0 at the end of March. |
Beta Was this translation helpful? Give feedback.
@wobbet I have live replication (#8) almost working. That'll let you have one writer node and multiple read-only nodes streaming changes in real-time. Is that what you're looking for? I'm hoping to have it finished and cleaned up by the end of the month and then spend most of March doing testing and performance improvements. It'll release with v0.4.0 at the end of March.