This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-15
Channels
- # announcements (1)
- # babashka (1)
- # beginners (43)
- # cider (2)
- # clj-kondo (29)
- # clojure (61)
- # clojure-austin (18)
- # clojure-dev (7)
- # clojure-europe (30)
- # clojure-nl (1)
- # clojure-norway (23)
- # clojure-uk (5)
- # clojuredesign-podcast (8)
- # cloverage (1)
- # conjure (1)
- # data-science (1)
- # datahike (36)
- # datavis (1)
- # datomic (23)
- # emacs (14)
- # hyperfiddle (28)
- # lsp (5)
- # missionary (1)
- # music (1)
- # off-topic (11)
- # re-frame (11)
- # reitit (5)
- # releases (1)
- # shadow-cljs (65)
- # spacemacs (13)
- # squint (33)
- # tools-deps (56)
is the dynamodb storage backend for Datahike reasonably up to date ?
there's more than one ? any
ok it looks like this is the only one it has https://github.com/csm/konserve-ddb
that one hasn't seen updates for 5 years so no. Datahike has seen a lot of development in recent years. Everything older than a year won't work with latest datahike version I assume
This is what was needed to support a S3 backend https://github.com/replikativ/konserve-s3/blob/main/src/konserve_s3/core.clj.
The main limitation this one still has is that it does not use an async client as well when the API would prefer it, but just wraps sync calls in go blocks. That is totally fine though to get started.
@U0CKDHF4L Would you be interested in helping with that?
Maybe the S3 backend would also work, it depends mostly on your latency requirements I think.
why S3 for dynamodb ? edit: oh you mean as an alternative would https://github.com/taoensso/faraday be of use ?
that would do, although direct java API calls should also be fine. whatever is simple to pick up and reliable
what does it need to store and retrieve ? is it just [e a v t op]
?
so there will be a blob column, but normally dynamo adds columns automatically as far as i understand
ohhhh yessss I remember
this is how it looks like for SQL if that helps https://github.com/replikativ/konserve-jdbc
@U0CKDHF4L can you contextualize how you would like to use dynamodb?
I don't have a preference really I just wondered. If there's an existing AWS backend that does the job then that's fine
(unless there's some advantage to dynamodb)
the first thing to improve though is to add proper async support to konserve-s3, it will reduce latency on S3
also dynamodb comes by default with aws services doesn't it ?
that you can access a dynamodb from anywhere by default without having to install it I thought
(I'm not that familiar with aws)