Comment

Comment by xiaomai

I've been running sqlite in production since 2014 (no litestream).

It'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).

parent xiaomai 2 years ago

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton