https://docs.datomic.com/on-prem/best-practices.html#consistent-db-value-for-unit-of-work

prefer making a DB once and passing as a value to an entrypoint or family of functions

if you need to tx, obviously pass a connection, but try to separate these concerns

don't do (d/db con) in the body of every function that does querying, for eg

pass db in as an argument

E.g. in an http-like request handler, it makes sense for it to get a conn and db once, then pass that db around

assuming an http request-response is a single unit of work (which it is most of the time)

helpful, thanks

checking this I think did this by commons sense without knowing but verifying anyway