This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-24
Channels
- # announcements (8)
- # aws (12)
- # babashka (84)
- # beginners (380)
- # calva (56)
- # clj-kondo (52)
- # cljdoc (4)
- # cljs-dev (327)
- # cljsrn (4)
- # clojure (154)
- # clojure-italy (5)
- # clojure-nl (3)
- # clojure-uk (21)
- # clojurescript (52)
- # conjure (133)
- # cursive (64)
- # datomic (33)
- # emacs (22)
- # fulcro (35)
- # graalvm (24)
- # graphql (1)
- # kaocha (1)
- # leiningen (1)
- # off-topic (24)
- # onyx (2)
- # pathom (10)
- # re-frame (3)
- # reagent (3)
- # reitit (3)
- # shadow-cljs (48)
- # spacemacs (12)
- # tools-deps (98)
- # xtdb (7)
Hi, unfortunately it's probably not going to be a suitable replacement for the time being. InfluxDB uses all kinds of columnar compression & storage techniques, with various aggregation utilities. You've reminded me though that it's worth an FAQ entry for the difference between a timeseries db and a temporal db 🙂
Well I'm quite new to all this 😉. I'm trying to figure out where crux fits in. Is there a use case for small/hobbiest projects? Or is it more geared towards business and advanced applications?
I can sympathise! And time is very confusing... Crux is definitely good for hobby things. We have quite a few small internal apps running on it. It's pretty simple and reliable. I would recommend RocksDB + Postgres, or RocksDB + SQLite if you really don't want have to set up Postgres for "fun" 🙂
@U899JBRPF so you would recommend SQLite over RocksDB for a single node Crux setup?
@U8ZN5EHGU I mean SQLite for the event-log (specifically). Using RocksDB for the event-log as well as the main kv store is a good choice too, but I suspect many people would consider it more opaque