i've created a blog post about how I handle routing in the context of Datomic Ions and AWS API Gateway. for anyone interested, am i missing something? https://medium.com/@rodeorockstar/datomic-ions-aws-api-gateway-and-routing-d20a1bb086dd

hi there, is this very bad?

WARNING: requiring-resolve already refers to: #'clojure.core/requiring-reso
lve in namespace: datomic.common, being replaced by: #'datomic.common/requi
ring-resolve

no, it’s not bad (that’s why it’s a warning)

I expect a newer version of something on the datomic side probably fixes it, but I’d defer to someone from the datomic team to verify that

I think requiring-resolve was introduced in 1.10, hence the name clash

yes, but name clashes are quite intentionally not a bug

so nothing is broken here, but newer versions can or do either silence the warning (by intentionally excluding it) or by switching to the version now in Clojure

(I’m not sure which of those potential actions has already been taken)

is there a logical/performance difference between these two:

[(missing? $ ?foo :bar)]
(not [?foo :bar])

With Datomic Cloud, if I need to fail/abort a transaction (i.e. validation failed) within a transaction function, can I just throw an exception? That's how it works with on-prem, but the docs for Cloud don't mention anything about aborting transactions from within a transaction function.

@mdhaney yup

Is there an official docker image for the Datomic Transactor from Cognitect? Has anyone used this one? https://hub.docker.com/r/pointslope/datomic-pro-starter/dockerfile/ Use case is: running transactors inside kubernetes to avoid running standby transactors (half the cost without the ec2 boot time) and better embrace resource usage within kubernetes (having less idle resources). cc @marshall