Ask HN: Are you using SQLite and Litestream in production?
11–20 of 26 posts
Re: Ask HN: Are you using SQLite and Litestream in production?
#12Re: Ask HN: Are you using SQLite and Litestream in production?
#13copying and pasting from a different thread because this keeps coming up and I want to share my experience in case it's helpful: I use SQLite/Litestream for https://extensionpay.com ! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great! I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesley…
Re: Ask HN: Are you using SQLite and Litestream in production?
#14It's mostly great. I love how easy it is to backup the database, mirror prod into my local environment for development, etc. Restoring things from backup is also quite nice: I can attach to the restored db and the prod db in the same sqlite session and update/insert the necessary records (w/ joins/etc.)
I'm starting to have to work around the single-writer limitation. I've got a web server and a set of background job workers. As my scale has increased, I've had to start working around write conflicts (I'm debating switching to postgres for this reason, but I know sqlite is working on concurrent writes, so I'm hoping they beat me to it).
Re: Ask HN: Are you using SQLite and Litestream in production?
#15I use sqlite with litestream through Pocketbase in production for around 2 years now on a site with 12,000 / month traffic. Works flawlessly and I haven't had to do anything to maintain it.
I've been tinkering with it over the last week, but have yet to hear of someone using it in production.
I'd love to hear more about your use case, and any other thoughts you can share when using PocketBase.
Re: Ask HN: Are you using SQLite and Litestream in production?
#16copying and pasting from a different thread because this keeps coming up and I want to share my experience in case it's helpful: I use SQLite/Litestream for https://extensionpay.com ! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great! I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesley…
Re: Ask HN: Are you using SQLite and Litestream in production?
#17copying and pasting from a different thread because this keeps coming up and I want to share my experience in case it's helpful: I use SQLite/Litestream for https://extensionpay.com ! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great! I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesley…
As someone considering a SvelteKit + SQLite stack, I would love to hear more about the setup. Have you considered writing a blog post on the topic? If this is too much, perhaps you can drop a few words here...
Re: Ask HN: Are you using SQLite and Litestream in production?
#18copying and pasting from a different thread because this keeps coming up and I want to share my experience in case it's helpful: I use SQLite/Litestream for https://extensionpay.com ! Serves about 120m requests per month (most of those are cached and don't hit the db), but it's been great! I was convinced that SQLite could be a viable db option from this great post about it called Consider SQLite: https://blog.wesley…
I've been struggling with the Postgres vs. SQLite decision lately, especially since my app runs on a single server (and will likely continue that way for a long time) but the real reason I am still leaning towards Postgres is for the ecosystem of monitoring tools and plugins. For example a big downside of SQLite is that I don't have easily available tools that can give me reports on slow queries, full table scans, an…
Re: Ask HN: Are you using SQLite and Litestream in production?
#19But we did run into some scariness around trying to use Litestream that put me off it for the time being. Litestream is really cool (and I'm a big fan of its author!) but it is also very much a cool hack in the way it works.
The scariness I ran into was related to this issue https://github.com/benbjohnson/litestream/issues/510
And after a bit more fiddling I came away nervous about the possibility of corruption, which is not something I want to worry about from my backup method.
So for now we're just doing regular snapshotting with remote backups and that seems sufficient with RAID1 storage. I would like something lower latency at some point but don't have the time at the moment to work on it.