This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-01
Channels
- # announcements (3)
- # beginners (59)
- # calva (23)
- # cider (58)
- # clojure (125)
- # clojure-dev (18)
- # clojure-dusseldorf (1)
- # clojure-europe (21)
- # clojure-germany (1)
- # clojure-hamburg (1)
- # clojure-italy (13)
- # clojure-nl (29)
- # clojure-poland (3)
- # clojure-spec (61)
- # clojure-uk (74)
- # clojurescript (12)
- # core-async (6)
- # cursive (4)
- # data-science (7)
- # datomic (14)
- # defnpodcast (1)
- # events (4)
- # fulcro (72)
- # juxt (36)
- # kaocha (3)
- # nginx (3)
- # off-topic (14)
- # pathom (5)
- # ring-swagger (68)
- # shadow-cljs (25)
- # spacemacs (8)
- # sql (42)
- # tools-deps (8)
- # vim (6)
does anyone have a recommendation for a simple embeddable keyvalue database? i am leaning towards lmdb, but was wondering if there is a de facto standard clojure community uses?
How much data do you want to store? Is it in-memory or should also be persisted to disk? How do you expect to query it? I think you will get much better recommendations if you can narrow down your requirements a bit 😉
data is market trade events. it is supposed to persist to disk and used for data analytics research and also fed to trading bots. I don't worry about the rate of incoming data being too high at the moment, simplicity and ease of use, availability of libs has more value to me.
https://github.com/replikativ/datahike looks interesting but I haven't yet started working with it
But given you're dealing with trade events. maybe a time-series database would be best? https://www.timescale.com (Postgres extension)