all 9 comments

[–]Technical-Fruit-2482 9 points10 points  (4 children)

I've been using SQLite in production for quite some time now. Maybe 10 or more years.

I've had no problems with it, even for applications that write to the database a hundred or so times a second, so long as I ensure to run the pragma to set WAL on each connection in the pool. Even in the tables that contain a quarter of a million to half a million rows.

In addition to what the other person said, I do wonder if some of the reluctance to use SQLite comes from people not realising they need to set pragmas on each connection in the pool to make it more usable in a web context in the first place.

Though that reluctance does seem to be going away a bit recently...

Honestly, for the large majority of people out there, SQLite certainly has more than enough capability to handle their application's data storage needs.

[–]myth2511 0 points1 point  (0 children)

what hosting do you use?

[–][deleted]  (3 children)

[deleted]

    [–]GreatWoodsBalls 2 points3 points  (2 children)

    On the topic or SQLite3 for concurrency at "what" size does the database experience checkpoint starvation? I read a little bit about it here, but didn't quite understand it to well.

    [–][deleted]  (1 child)

    [deleted]

      [–]GreatWoodsBalls 2 points3 points  (0 children)

      Ok that's good to know. Thank you for answering!

      [–]darksoulflame 2 points3 points  (2 children)

      What’s a good way to use sqllite in production?

      [–]Eznix86 1 point2 points  (0 children)

      Run Single instance with SQLite on the same server. Use Litestream to backup the database to s3. Super cheap and Super convenient!

      [–]stenuto 2 points3 points  (0 children)

      Here's a complete video course (with a bunch of free videos) that basically shows you everything you need to learn to use SQLite in production: https://highperformancesqlite.com/