I'm very much looking forward to this series. I've been following the progress of XTDB, a relatively new, open source, bitemporal database for a while because we have some business problems at work -- online dating -- that would be easy to solve with it (but are hard with traditional databases). See https://www.xtdb.com/ for more details (their upcoming 2.0 release switches to a columnar architecture and provides a full SQL interface, in addition to Datalog).
Practically, where is the "complexity budget" to be found? How do you create it, think about it? This fundamental gap between the phrase and practical use, makes the idea a non-starter.
That last phrase was good, left me wanting to read your next post 👍
Mwahahaha 😹
I'm very much looking forward to this series. I've been following the progress of XTDB, a relatively new, open source, bitemporal database for a while because we have some business problems at work -- online dating -- that would be easy to solve with it (but are hard with traditional databases). See https://www.xtdb.com/ for more details (their upcoming 2.0 release switches to a columnar architecture and provides a full SQL interface, in addition to Datalog).
Practically, where is the "complexity budget" to be found? How do you create it, think about it? This fundamental gap between the phrase and practical use, makes the idea a non-starter.