This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-13
Channels
- # announcements (4)
- # babashka (1)
- # beginners (124)
- # calva (5)
- # cider (3)
- # clara (3)
- # clerk (5)
- # clj-commons (14)
- # cljdoc (12)
- # cljs-dev (14)
- # clojure (43)
- # clojure-austin (23)
- # clojure-europe (55)
- # clojure-nl (1)
- # clojure-norway (11)
- # clojure-uk (2)
- # clojurescript (34)
- # conjure (1)
- # cursive (1)
- # data-science (28)
- # datomic (3)
- # fulcro (20)
- # gratitude (2)
- # hyperfiddle (6)
- # introduce-yourself (1)
- # jobs (5)
- # lsp (56)
- # malli (5)
- # membrane (7)
- # mount (5)
- # off-topic (16)
- # polylith (39)
- # portal (38)
- # practicalli (1)
- # rdf (1)
- # re-frame (8)
- # releases (8)
- # remote-jobs (4)
- # shadow-cljs (49)
- # sql (1)
- # xtdb (36)
When calling Client API https://docs.datomic.com/client-api/datomic.client.api.html#var-tx-range with Datomic Cloud, why is there DynamoDB usage? Is it, in fact, precisely... reading the tx log solely from DynamoDB b/c it's the source of truth for the tx log?
Follow up question, this can cause OpsPending and OpsTimeout metrics bumps.
Is that because we're waiting for DynamoDB to scale up its read capacity, and since Datomic doesn't really need much read capacity from DDB, it's not in the habit of aggressively scaling it up?
The context is: making tx log backups.
that's what dynamodb is to cloud: tx-log