# Looking for Best Practices for Modeling Evolving Entities in Datomic?
**URL:** https://forum.datomic.com/t/looking-for-best-practices-for-modeling-evolving-entities-in-datomic/2566
**Category:** General
**Created:** [June 25, 2025, 4:23am UTC](https://forum.datomic.com/t/looking-for-best-practices-for-modeling-evolving-entities-in-datomic/2566 "2025-06-25T04:23:40Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@danielljose](https://forum.datomic.com/u/danielljose)
#### Post date: [June 25, 2025, 4:23am UTC](https://forum.datomic.com/t/looking-for-best-practices-for-modeling-evolving-entities-in-datomic/2566/1 "2025-06-25T04:23:40Z")
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-keys](https://docs.datomic.com/reference/best.html#unique-ids-for-external-keys)[sql course in hyderabad](https://www.igmguru.com/microsoft-training/microsoft-sql-training-in-hyderabad)
but still need some more help.
Thanks in advance !!
Daniel
---
### Author:  [@system](https://forum.datomic.com/u/system)
#### Post date: [June 25, 2025, 12:26pm UTC](https://forum.datomic.com/t/looking-for-best-practices-for-modeling-evolving-entities-in-datomic/2566/3 "2025-06-25T12:26:00Z")