This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-29
Channels
- # aleph (4)
- # architecture (12)
- # bangalore-clj (1)
- # beginners (87)
- # boot (3)
- # cider (19)
- # cljs-dev (84)
- # clojars (10)
- # clojure (79)
- # clojure-italy (7)
- # clojure-nl (19)
- # clojure-russia (10)
- # clojure-spec (9)
- # clojure-uk (55)
- # clojurescript (64)
- # core-async (7)
- # core-typed (4)
- # cursive (7)
- # data-science (2)
- # datomic (8)
- # devcards (6)
- # docs (1)
- # duct (5)
- # fulcro (117)
- # graphql (1)
- # instaparse (1)
- # leiningen (13)
- # lumo (103)
- # nyc (3)
- # off-topic (54)
- # om (9)
- # onyx (1)
- # pedestal (6)
- # planck (3)
- # portkey (7)
- # re-frame (26)
- # reagent (20)
- # ring-swagger (14)
- # shadow-cljs (164)
- # sql (11)
- # tools-deps (25)
- # yada (1)
@chrisblom if you have a lot of it, it's not ideal.
yeah i’m finding out that its not a great fit, we currently have a database that keeps on growing, with no good way to remove old data
I think Nubank do something where they create new databases regularly, but that depends on a complex aws setup from what I recall.
i’m also looking into the timescale plugin for postgres, but no AWS RDS support yet unfortunately
@chrisblom if you want a “sliding window” snapshot of the data, you can store it in kafka or some unindexed store, and then load it into a memory datomic db at fixed intervals