This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-27
Channels
- # announcements (1)
- # asami (10)
- # babashka (12)
- # beginners (26)
- # biff (4)
- # calva (42)
- # cider (1)
- # clj-commons (2)
- # cljs-dev (2)
- # clojure (179)
- # clojure-dev (2)
- # clojure-europe (45)
- # clojure-norway (16)
- # clojure-uk (3)
- # clojurescript (5)
- # datahike (1)
- # datascript (2)
- # events (3)
- # exercism (1)
- # fulcro (13)
- # funcool (3)
- # graalvm (23)
- # helix (3)
- # honeysql (1)
- # hyperfiddle (3)
- # lsp (51)
- # malli (2)
- # off-topic (27)
- # portal (18)
- # reagent (3)
- # reitit (3)
- # releases (8)
- # sci (5)
- # shadow-cljs (11)
- # xtdb (5)
are there tutorials/resources for writing a custom transaction log store or index store?
hey @U050S5ZET we haven't documented the exact protocol requirements, but you can basically look at any of the implementations (JDBC, filesystem, Kafka) to get a feel for what's involved. You can also run isolated tests for those protocols to validate your implementations. What backend storage are you considering?
Thanks. Mostly just curious. But i’m also curious why Dynamodb isn’t an option for the tx log or index, since S3 is supported for doc storage.