Hacker News new | past | comments | ask | show | jobs | submit login

That’s a very cool addition! I wonder if this can be used in an event sourcing architecture with minimal overhead.



I think to be really useful an event sourcing data store needs `as at` support in addition to `as of` (i.e. bitemporality) to cope with retroactive and proactive events and corrections. There are a couple of references for this in the Crux docs: https://juxt.pro/crux/docs/bitemp.html#_known_uses




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: