Conversation

Notices

1. Embed this notice
   Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 22-Aug-2023 12:38:57 JST Alex Gleason
   SQLite is so much better than people think. https://www.twilio.com/blog/sqlite-postgresql-complicated
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 22-Aug-2023 12:46:12 JST Alex Gleason

     in reply to

     • verita84 :Debian_logo: :firefox: :bing: :android:
     @verita84 The worst performing SQLite library in JavaScript still does over 600K ops/second.
   • Embed this notice
     verita84 :Debian_logo: :firefox: :bing: :android: (verita84@poster.place)'s status on Tuesday, 22-Aug-2023 12:46:13 JST verita84 :Debian_logo: :firefox: :bing: :android:

     in reply to
     @alex
     
     it was so bad with Nextcloud that they stopped supporting it and made people use MySql or Postgres
   • Embed this notice
     mikedilger (ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49@mostr.pub)'s status on Wednesday, 23-Aug-2023 01:11:57 JST mikedilger

     in reply to
     That link doesn't support your case. PostgreSQL beat SQLite on every metric he tried. And he kept PostgreSQL's hands tied behind it's back by using only the intersection of features via an ORM and barely touching performance tweaks.
     
     SQLite is a weird mutant. It is an RDBMS SQL database designed to be a persistence layer of a single application. It doesn't work as the former (not a server) nor is it well suited for the latter (kv databases work better as I have recently learned through experience). I think they did a great job of building the mutant to be the best mutant possible, but I don't see the use case anymore.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 23-Aug-2023 01:11:57 JST Alex Gleason

     in reply to

     • mikedilger
     @ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49 It outperformed Postgres querying large time-based datasets. Eg "trending hashtags in the past year".
     
     Key-value stores will give you more performance of course, but you are essentially building a custom datastore.
     
     SQLite is great for being an all-in-one embedded solution, and I'm gonna love it until I witness the performance being bad firsthand.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 23-Aug-2023 01:37:04 JST Alex Gleason

     in reply to

     • Snugglefist
     • mikedilger
     • elaine
     @snugglefist @ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49 Yes. @elaine is working on something with neo4j. I'm trying to use only embedded databases for my project.
   • Embed this notice
     Snugglefist (snugglefist@freezepeach.online)'s status on Wednesday, 23-Aug-2023 01:37:12 JST Snugglefist

     in reply to

     • mikedilger
     Aren't graph databases better suited for queries like "users who liked this post"?