Yes. And probably the best characteristic of SQLite in production is its (albeit accidental or implied) story around Dev/Ops. A whole category of problems just goes away.
Ask HN: Have you used SQLite as a primary database?
211–220 of 330 posts
Re: Ask HN: Have you used SQLite as a primary database?
#212Here's an all-time great post about why you might consider SQLite in production with data about performance: https://blog.wesleyac.com/posts/consider-sqlite I use SQLite in production for my SaaS[1]. It's really great — saves me money, required basically no setup/configuration/management, and has had no scaling issues whatsoever with a few million hits a month. SQLite is really blazing fast for typical SaaS workloads…
This was so inspiring to read. It's a very balanced take about the pros and cons of using SQLite vs. Postgres at scale. I say "inspiring" because using SQLite reminds me of the simplicity and productivity from coding for the "early web" that lost 10-15 years ago. The days when you could spin up a website without worrying about a bunch of ancillary services and focus on the app itself. For me, SQLite's lack of online…
I have this beef too. Tooling for dumping and restoring into a new schema are easy/simple/fast. So, these schema migrations can happen w/o issue. Some tricks with the PRAGMA directive in SQLite so you can roll out changes (eg: code supports old/new schema while migrating)
Re: Ask HN: Have you used SQLite as a primary database?
#213Here's an all-time great post about why you might consider SQLite in production with data about performance: https://blog.wesleyac.com/posts/consider-sqlite I use SQLite in production for my SaaS[1]. It's really great — saves me money, required basically no setup/configuration/management, and has had no scaling issues whatsoever with a few million hits a month. SQLite is really blazing fast for typical SaaS workloads…
What is the point of using SQLite under a web service? I thought people complained how MySQL sucks and PostgreSQL rocks for being right and SQLite was nowhere near being right or performant. (Things seem to be getting better with strict column types these days.) I've recently migrated a smallish service from MySQL to PostgreSQL and figured it's quite a work if you're not careful writing by the SQL standard which mean…
> I thought people complained how MySQL sucks and PostgreSQL rocks for being right and SQLite was nowhere near being right or performant
While "people" complaining is basically meaningless, I don't know why they'd be doing that about SQLite. It's used in most phones, all copies of Windows 10+, and countless other places.
Re: Ask HN: Have you used SQLite as a primary database?
#214Earlier quoted context omitted.
> hits a month Is not a very useful performance metric. What is your peak hits per second?
I love watching people use "x per month" as some sort of architecture selection argument, especially when these arguments conclude in a proud justification of cloud sprawl. There are single node/CPU solutions that can process 10-100 million business events per second . I am almost certain that no one logged into HN right now has a realistic business case on their plate that would ever come close to exceeding that cap…
ESAIDBUSINESSTOOMANYTIMES
Re: Ask HN: Have you used SQLite as a primary database?
#215I love sqlite3. In python: https://docs.python.org/3/library/persistence.html
I have of course pickle -> open()
But eventually my projects grow large enough that sqlite3 becomes the database. I have never needed to go beyond sqlite3 in my projects. It does everything I ever need it to do.
Re: Ask HN: Have you used SQLite as a primary database?
#216Here's an all-time great post about why you might consider SQLite in production with data about performance: https://blog.wesleyac.com/posts/consider-sqlite I use SQLite in production for my SaaS[1]. It's really great — saves me money, required basically no setup/configuration/management, and has had no scaling issues whatsoever with a few million hits a month. SQLite is really blazing fast for typical SaaS workloads…
how do you handle things like encryption and access permissions?
The only thing I have against using SQLite in production (for my needs) is the lack of at rest encryption and row level permissions by user.
Re: Ask HN: Have you used SQLite as a primary database?
#217[deleted]
Re: Ask HN: Have you used SQLite as a primary database?
#218VATcomply.com has been using SQLite as a primary database for 2 years and is serving ~70 requests per second without an issue.
HTTPS: https://vatcomply.com/ Github: https://github.com/madisvain/vatcomply
Re: Ask HN: Have you used SQLite as a primary database?
#219Earlier quoted context omitted.
- Setting up a MySQL server on both your dev machine and server, and making sure they're the same version (extra fun if they're on different OS versions) - Setting up an out-of-repo config file on the server with your MySQL credentials - Setting up a backup script for your server data It's only about an hour of work total, but it's an hour of work that I hate doing.
docker-compose is the way to go for keeping the dev versions synced with the production version. And for the backup script scheduled mysqldump and copy to storage should see you through quite far, so not really any more effort than copying an SQLite database.
and now you need to learn docker and 10 other things.
Re: Ask HN: Have you used SQLite as a primary database?
#220The old(ish) Cyanide implementation of Blood Bowl used SQLite as the data store for all of the game data. It worked, but the game startup time was absolutely dominated by loading data from the database and took too long even on a fast SSD.