Litestream Alternatives
Similar projects and alternatives to litestream
-
-
-
Scout APM
Scout APM: A developer's best friend. Try free for 14-days. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.
-
-
nfs-subdir-external-provisioner
Dynamic sub-dir volume provisioner on a remote NFS server.
-
-
sqlcipher
SQLCipher is an SQLite extension that provides 256 bit AES encryption of database files.
-
-
-
Jekyll
:globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
-
-
-
sqlitebrowser
Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:
-
-
-
s6-overlay
s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
-
-
k8s-mediaserver-operator
Repository for k8s Mediaserver Operator project
-
kubernetes-the-hard-way
Bootstrap Kubernetes the hard way on Google Cloud Platform. No scripts.
-
-
up
Ultimate Plumber is a tool for writing Linux pipes with instant live preview (by akavel)
Reviews and mentions
-
Back to basics: Writing an application using Go and PostgreSQL
If by persist to disk you mean "when you're done", it can by replicating the db to a file. Another option is to back it up over the network, e.g., https://github.com/benbjohnson/litestream
I had the same objection to SQLite, and then I heard about Litestream, and it won me over.[0]
Litestream watches your SQLite database and then streams changes to a cloud storage provider (e.g., S3, Backblaze). You get the performance and simplicity of writing SQLite to the local filesystem, but it's syncing to the cloud. And the cool part is that you don't have to change any of your application code to do it - as far as your app is concerned, it's writing to a local SQLite file.
I wrote a little log uploading utility for my business that uses Litestream, and it's been fantastic.[1] It essentially carries around its data with it, so I can deploy my app to Heroku, blow away the instance and then launch it on fly.io, and it pops up with the exact same data.[2]
I'm currently in the process of rewriting an open-source AppEngine app to use SQLite + Litestream instead of Google Firestore.[2] It's such a relief to get away from all the complexity of GCP and Firestore and get back to simple SQLite.
[1] https://mtlynch.io/litestream/
[2] https://asciinema.org/a/I2HcYheYayeh7aHj23QSY9Vyf/embed?size...
-
Ask HN: Using SQLite for server/client web apps?
This might be of interest: https://litestream.io/
- Securing your application credentials and other sensitive keys
-
What's your side project written in Kotlin?
Something like Litestream?
-
Your Pull Request is not a gift
There was a recent example of a project that followed this strategy: Litestream. Initially, Litestream was closed to external contributions because it was too expensive for the maintainer team to handle them. As I said before: reviewing Pull Requests costs time and money. If there is not enough time or money, a project can simply choose to not accept external contributions. Fast forward, Litestream now accepts bug fixes contributions, but no features. Bug fixes are slightly easier to handle as they are clearly scoped and most of the time the number of changes is small.
- Litestream: Streaming Replication for SQLite
-
What is the best approach in order to send the database state to a server periodically?
Have you seen litestream.io, for SQLite?
-
RIP Jekyll (The Genesis of the Jamstack)
Just don't do any of that stuff if you don't want to. If you're writing software because it's useful to yourself and others and making it open to others to use you do not owe them a place to chat, engagement, a roadmap, a release cycle (or any given release).
You can weigh whether you want to do those things
Those things are often set up when people want to run software projects with certain goals and if those goals are not yours then that is fine, just know that there is a tradeoff.
One nice example is litestream[0]. It's open source, not open contribution -- similarly you can have open source without built in community/discord/project-management/etc.
[0]: https://github.com/benbjohnson/litestream#open-source-not-op...
-
Recommendation for app deployment
Here’s a good tool for tacking more “production” features, like replication, for SQLite: https://litestream.io/ basically, your DB is constantly synced from an object store like S3 to your app.
-
A Future for SQL on the Web
People are already trying to get me to hook up https://litestream.io/ to it
-
Are managed Kubernetes and managed databases worth it for a one-man show?
Database wise, depending on your expected load I'd say stick with sqlite. This is especially nice if you combine it with litestream.io which streams any changes to the database to object storage every second by default. It doesn't allow you to run multiple instances of the same database but it can get you really far when you scale vertically. After that you'll probably know better what you require from your stack.
-
Local k3 or k8 cluster - What are you using for persistent storage for sonarr/radarr etc?
I'm a bit surprised I haven't seen this one mentioned here yet as it's specifically about SQLite databases: https://litestream.io
-
k8s-mediaserver-operator - Your all-in-one resource for your media needs! - Plex/Jackett/Radarr/Sonarr/Transmission with ARM support!
There is also https://litestream.io/
-
Maddy: Composable all-in-one mail server
I used to run my own mail, but gave up due to the risk of me screwing up backups.
Maddy + https://litestream.io/ might be simple enough to get right.
Stats
benbjohnson/litestream is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.