Replies: 2 comments 4 replies
-
Thanks, Tom. It is possible to embed as a library, however, it's GPL3-licensed (which can affect the embedder's software's license) and I'm not making a commitment on the public API right now. Once Litestream hits 1.0 then I'll write some docs for how to embed it in an application. On the other hand, I like that Litestream is an operational concern instead of a development concern. I find it easier if I don't need to worry about additional dependencies while I'm writing an application. |
Beta Was this translation helpful? Give feedback.
-
I think that embedding this functionality is similar to the idea of embedding DB functionality. Simplifies service dependencies and so on. While some may balk at the GPL constraint; that’s your choice. Either way, thanks for the work on the software that tries to reduce overall complexity; the trend these days has been to pile on more complexity for little gain. |
Beta Was this translation helpful? Give feedback.
-
Part of the single-server approach and deployment could be made even easier if litestream ran embedded in the application itself. For a Go-based application, It can be run as a goroutine. Some examples or pathways to easy adoption with this style would be a great addition to https://litestream.io/guides/
(It's also very possible that this is already solved in a way I'm not aware of.)
Beta Was this translation helpful? Give feedback.
All reactions