This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-10
Channels
- # admin-announcements (1)
- # aleph (1)
- # asami (9)
- # babashka (30)
- # beginners (83)
- # calva (8)
- # cherry (4)
- # cider (4)
- # clj-kondo (15)
- # cljs-dev (11)
- # cljsrn (8)
- # clojure (85)
- # clojure-europe (87)
- # clojure-losangeles (9)
- # clojure-nl (4)
- # clojure-norway (4)
- # clojure-spec (3)
- # clojurescript (12)
- # community-development (5)
- # conjure (1)
- # core-typed (3)
- # datomic (21)
- # docker (13)
- # emacs (13)
- # funcool (1)
- # google-cloud (1)
- # graalvm (12)
- # gratitude (14)
- # holy-lambda (6)
- # introduce-yourself (18)
- # lsp (15)
- # malli (6)
- # matcher-combinators (15)
- # nbb (15)
- # off-topic (37)
- # pathom (31)
- # portal (23)
- # rdf (3)
- # releases (2)
- # reveal (2)
- # sci (4)
- # scittle (3)
- # shadow-cljs (14)
- # squint (2)
- # tools-deps (29)
Hi everyone, I have a question about serial/parallel transactions processing. If I have multiple databases running on single transactor, does it makes it any possible to runs txs in parallel to separate dbs?
I remember datomic transactions are not parallel by design to omit locks and other complicated stuff, but still curious if it's per db or for the whole transactor
Not sure if you're planning to use on-prem or cloud, but I recommend reading this post and making sure what you're planning to do aligns with the recommendations from marshall and rich https://forum.datomic.com/t/multi-tenancy-databases/238
I followed the datomic cloud setup guide, but when attempting to connect to the system I get an error
;;; deps.edn
{:deps
{com.datomic/dev-local {:mvn/version "1.0.243"}
com.datomic/client-cloud {:mvn/version "1.0.119"}}
:mvn/repos {"datomic-cloud" {:url ""}}}
(def client1 (d/client {:system "mysystem1234"
:server-type :ion
:region "us-east-1"
:endpoint ""}))
ExceptionInfo Unable to connect to
{:cognitect.anomalies/category :cognitect.anomalies/unavailable,
:cognitect.anomalies/message "DNS timeout 5000 ms",
:config {:system "mysystem1234",
:server-type :cloud,
:region "us-east-1",
:endpoint "",
:endpoint-map {:headers {"host" ""},
:scheme "http",
:server-name "",
:server-port 8182}}}
Any tips on how to start debugging this?Check your template outputs via aws cloudformation describe-stacks --stack-name <compute-stack>
and look for your ClientApiGatewayEndpoint
in the output and grab the https url value. Replace your
""
with the ClientApiGatewayEndpoint.Reading through https://docs.datomic.com/cloud/tutorial/client.html describes the ClientApiGatewayEndpoint
.
I was looking at https://docs.datomic.com/cloud/getting-started/start-system.html
I don't seem to have ClientApiGatewayEndpoint
in the compute stack output
there is no such thing as a solo topology anymore, we consolidated solo+production topology while supporting scaling down to the original "solo" size (and cost).
Strange, it's still listed as an option when you step through the aws marketplace listing
Once you "subscribe" to datomic-cloud in the aws marketplace you can create a system by using the storage and compute stacks under the "Current Releases" section of that link.
If you get stuck again please reach out. (unfortunately we are currently unable to remove the solo topology from the drop-down in the aws marketplace)
That worked, thanks! Small point on the docs, it would be useful to mention somewhere on https://docs.datomic.com/cloud/operation/new-system.html#storage that the stack name of the storage stack is the system name. (I see it's mentioned https://docs.datomic.com/cloud/operation/storage-template.html#stack-name). That was my one snag