Looking for Best Practices for Modeling Evolving Entities in Datomic?

Hi all,

I have been working with Datomic for a few months now and absolutely loving the immutability and time-travel features. One area I am still wrapping my head around is modeling entities that evolve over time—like user profiles or configurations—especially when those changes need to be audited or rolled back.

I understand that Datomic encourages additive changes.., but I am wondering:

What are some best practices for managing evolving schemas or attributes: ??

Is it common to use component entities to represent “versions” of a logical entity: ??

How do you balance performance with historical tracking: ??

I would really appreciate examples or even links to open-source schema designs if available. I’ve read through the official docs, but real-world experiences would help me a lot. I have also gone through this resource https://docs.datomic.com/reference/best.html#unique-ids-for-external-keyssql course in hyderabad
but still need some more help.

Thanks in advance !!

Daniel