Does datomic need to particpate in a dependency injection framework?

I think the answer to the topic title’s question is “No” because datomic.api/connect returns a cached connection object. What do you think? Do you end up putting datomic in your DI framework (donut, mount, component, etc…)

We use component to inject multiple connections into our app code. Though the lifecycle support is not strictly necessary because d/connect is idempotent, we found it useful for managing different configurations and adding a little bit of indirection. It’s also a good place to add d/filter rules