3 ms·
The temporal support seems handy, but time is still going to be really tricky for financial systems. Datomic only covers what the physical state of the database
by slaymaker1907 3y ago
The temporal support seems handy, but time is still going to be really tricky for financial systems. Datomic only covers what the physical state of the database was at a particular time, but there's also the effective legal time (maybe a payment was dated a day before the system actually processed it) as well as requirements to remove data after a period of time (including point in time stuff).
- augustl 3y agoIndeed, it depends a lot on the domain. Datomic only has "technical" database time, and doesn't have any built-in way of modelling domain time. You can set the transaction timestamp manually when you write, but you can't set it to be earlier than the latest transaction that was committed. So, if you want your domain modelling to piggyback on Datomic time travelling, you can only do things like delaying writes for, say, an hour, and hope you have all the data by the time you commit to db.
- nlitened 3y agoThere's a bitemporal Datomic-like database from JUXT that does exactly that, I believe https://www.xtdb.com https://www.xtdb.com