This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-04-25
Channels
- # announcements (4)
- # beginners (26)
- # calva (18)
- # cider (24)
- # clojure (35)
- # clojure-brasil (9)
- # clojure-dev (6)
- # clojure-europe (39)
- # clojure-madison (1)
- # clojure-nl (1)
- # clojure-norway (100)
- # clojure-uk (6)
- # clojurescript (17)
- # data-science (15)
- # datalevin (5)
- # emacs (1)
- # events (2)
- # introduce-yourself (2)
- # javascript (1)
- # malli (28)
- # missionary (7)
- # off-topic (59)
- # polylith (20)
- # reitit (2)
- # releases (1)
- # remote-jobs (2)
- # rewrite-clj (5)
- # shadow-cljs (27)
- # sql (5)
- # squint (63)
- # xtdb (8)
👋 I've been reading some blog posts about using SQLite as a server database, and it got me curious. Anyone that tried it could share their experience? My use-case would have low traffic, low amount of writes and def low concurrency, so it sounds like a great fit without the overhead of Postgres. DB would be backed up via https://litestream.io/
cljdoc uses sqlite for its db, and it's open source
https://github.com/cljdoc/cljdoc/blob/master/src/cljdoc/storage/sqlite_impl.clj
SQLite is mostly used for one-user applications like browsers, messagers, etc. When it's used on the server, your client may face blocking exceptions when two clients write something. Even if you think it's rarely, it's still possible. Why not using postgres/mysql?
@U1WAUKQ3E I'm familiar with SQLite for mobile and single-user. However, with some tweaks it looks like it's fine e.g. https://fly.io/blog/all-in-on-sqlite-litestream/, also the official docs mention this https://www.sqlite.org/whentouse.html Reg "why not postgres/mysql": eh why not? I like SQLite and I'm curious about using it in this manner. Instant benefits are: one less thing to manage, easy backups, fast. Downsides are what you mentioned, but see linked docs. @U02N27RK69K nice thanks I'll check it out