The Crux of Bitemporality
summary
Crux is an open‑source bitemporal document database that preserves transaction time and adds flexible valid time so you can write corrections into the past. It ingests via Kafka (single ordered transaction topic, partitioned document topic), indexes into local RocksDB or LMDB, and supports compare‑and‑swap transactions, lazy queries compiled to worst‑case‑optimal joins, and targeted evictions for GDPR. The project is an alpha release from Juxt, runs as embedded JAR or cluster nodes, and is demonstrated live and usable now.
AI-written summary · about
chapters (15)
- 0:00Introduction and thanks
- 1:04Time in software systems
- 3:29Timestamping and its flaws
- 7:03Temporal databases evolution
- 11:19What is bitemporality?
- 14:07Use cases for bitemporal data
- 21:50Building Crux database
- 23:18Launching Crux live
- 24:29What is Crux?
- 25:11Crux architecture overview
- 31:11Bitemporal queries in Crux
- 33:41Query performance and design
- 36:50Crux layers and extensibility
- 39:20Crux community and future
- 41:07Q&A session
related talks
46mEnhancements to the bitemporal model support: integrity constraints
34mTransistor, a bitemporal database client
01h 06mReconstructing History with XTDB
32m"State of XTDB"
36mCrateDB: A Search Engine or a Database? Both! #bbuzz
36mRicher SQL — Steering SQL's Future Towards Clojure's Philosophy
42mBack to the Future! Time Travel with Bitemporal Databases
26mTemporal: A Better Way to Build Modern Applications