This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-10
Channels
- # announcements (9)
- # aws (11)
- # babashka (37)
- # beginners (97)
- # biff (2)
- # calva (73)
- # clj-kondo (17)
- # cljfx (3)
- # clojure (89)
- # clojure-europe (45)
- # clojure-norway (12)
- # clojurescript (17)
- # datahike (8)
- # datomic (13)
- # deps-new (4)
- # figwheel-main (1)
- # graalvm (2)
- # hyperfiddle (8)
- # introduce-yourself (6)
- # leiningen (38)
- # lsp (57)
- # malli (13)
- # nbb (46)
- # off-topic (40)
- # pathom (3)
- # polylith (8)
- # rum (4)
- # shadow-cljs (14)
- # spacemacs (1)
- # sql (11)
- # xtdb (10)
Another try. If you are using Datahike in production, what has been your experience so far?
Hi @U078GPYL8, there are some projects using Datahike in production. Even large ones are using it. I guess it is currently more suited for small to middle projects since we are still working on performance-improvements.
I am using it in production for 6 months. It works well. What fucked me up already 2 times is a database corruption. Could have been out of memory issue or unclean shutdown. In dont know. What bothers me is that the backup / restore procedure is buggy (need to manually patch the dump) and there are incompatibilities with 0.4 and 0.5 so upgrade path is blocked.
Performance is an issue.. its slower than a mongodb with same functionality. What is much slower are writes.. so I had to group writes together.
Queries performance is ok. It ls definitely slower than mongodb .. but the cleaner syntax is worth it.
Sb corruption is my biggest concern. So what I do now is I once a day write a random value to the db and then I don read to see if it gets the same value back. I cannot say if this trick works because I implemented it after the last corruption.
@UCSJVFV35 Thanks for the detailed feedback.