This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-04-09
Channels
- # aleph (1)
- # asami (5)
- # babashka (4)
- # beginners (8)
- # biff (19)
- # calva (2)
- # cider (14)
- # clojure (17)
- # clojure-dev (3)
- # clojure-europe (3)
- # clojurescript (2)
- # community-development (9)
- # conjure (1)
- # core-typed (2)
- # datomic (6)
- # emacs (20)
- # gratitude (1)
- # helix (5)
- # kaocha (4)
- # nbb (1)
- # releases (3)
- # testing (17)
Is there a "simple" way to deploy Datomic on prem to another cloud (GCP / GKE in this case) .. or is XTDB a better use case for minimizing deploy overhead for startup type things while retaining graph db / time series capability?
Quick question about Datomic Cloud: Is something like https://clojurians.slack.com/archives/C03RZMDSH/p1637930455444200?thread_ts=1637836254.435900&cid=C03RZMDSH still the best option wrt GDPR compliance? What about (off the top of my head) one db per user, which then gets deleted on request?
Is it viable to have n relatively small databases?
https://vvvvalvalval.github.io/posts/2018-05-01-making-a-datomic-system-gdpr-compliant.html#background:_about_the_gdpr outlines something similar to the above.
❓ Relatedly, is it still true of Cloud that queries cannot join across databases?
in my experience both in a dev-local and in an ion environment you can join across databases (as in provide multiple databases as inputs to d/q), BUT when connected to an ion server from outside of AWS, then you will get an error about it
Huh! Partial support?