I put 7 years of meal data in Datomic - Here's what I learned
summary
Seven years of meal plans go into Datomic as concrete facts and produce a schema of users dishes and recipes, then datalog queries and the entity API reveal counts trends and exact times things changed. Transactions are append-only and backdatable so 7 years of meal plans becomes a searchable timeline, enabling time-travel queries to find who changed what when and to replay or revert state. Architecture details include a single-writer transactor with peer reads and the use of Datascript to push client state via SSE.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:10What is Datomic
- 0:57Who is Christian
- 2:04Datomic logo
- 4:08Datomic model
- 6:14Transactor
- 7:35Peer Process
- 9:02Peer Server
- 10:06Data Model
- 14:00Database
- 14:32Schema
- 24:16Datalog
- 24:56Facts
- 28:54Query
- 30:01Create Database
- 32:47Create Entity
- 35:31Query Transaction
- 38:58Historical Data
- 44:58Speculative Changes
- 46:42Data Script
related talks
37m11 insights after 11 years with the functional database Datomic
37m11 insights after 11 years with the functional database Datomic
46mThe Datomic Architecture and Data Model
40mThe power of Datomic database
35mIt's Just Data
41mReal-World Datomic: An Experience Report
42mYet & Datomic Immutable Facts Mutated Our Stack
41mExploring four hidden superpowers of Datomic