Understand Datomic as an immutable, time-aware database model and how its architecture changes application design.
This section bridges the chapter overview and the detailed lessons below. For Java engineers, the practical question is how to handle Datomic architecture for Java engineers learning Clojure in Clojure code at the database boundary.
| Review focus | What to check |
|---|---|
| Facts over rows | Model changes as durable facts rather than in-place mutation. |
| Time | Use history as a design capability, not an audit afterthought. |
| Application role | Let Clojure query and compose immutable database values. |
Use the child lessons to move from concept to implementation. The section goal is to make the trade-off visible before the code hardens around a database assumption.