We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Analysis Summary
Ask yourself: “What would I have to already believe for this argument to make sense?”
Worth Noting
Positive elements
- This video provides a concise, high-density technical breakdown of the fundamental data unit in Datomic, useful for software architects evaluating database internals.
Influence Dimensions
How are these scored?About this analysis
Knowing about these techniques makes them visible, not powerless. The ones that work best on you are the ones that match beliefs you already hold.
This analysis is a tool for your own thinking — what you do with it is up to you.
Related content covering similar topics.
Datomic Cloud - Getting Started
ClojureTV
The Taming of the Deftype Baishampayan Ghose
Zhang Jian
Exercism Summer of Sexp - solving challenges with Clojure
Practicalli
Understanding Core Clojure Functions Jonathan Graham
Zhang Jian
The Data Reader's Guide to the Galaxy Steve Miner
Zhang Jian
Transcript
in de Tomic a database value is a collection of datums a datum is an atomic fact that represents the addition or a retraction of a relation between an entity and attribute a value in the transaction a datum is expressed as a five tuple an entity ID an attribute a value for the attribute each transaction ID a boolean indicating whether the datum is being added or retracted transactions can be about multiple entities and the transactions themselves are one or more datums an entity can consist of datums with any attributes defined by the schema because all datums are part of a single relation this is called a universal relation every transaction is assigned a transaction ID that is unique within the database transactions are fully serialized in the transaction IDs increase over time so transaction IDs are a total ordering of all transactions every datum includes the ID of the transaction that added the datum the transaction ID is in the TX position transaction IDs are themselves entity IDs since entities are just a bunch of datums with the same entity ID transactions can have datums that describe them the atomic assigns a DB TX instant for every transaction so every transaction knows the wall clock time it was recorded in the database the atomic uses multiple indexes to efficiently access datums in different sort orders the indexes are automatically managed by de Tomic and atomic utilizes the appropriate indexes in the query engine and pull API you can also directly access the indexes via the datums API if you need to with these indexes and universal relation you can model tables Collins documents and graphs de tama can navigate references bi-directionally so you don't need to model relationships in both directions a date omec database is a set of datums that each have their own entity attribute value transaction ID and operation it's really that simple
Video description
Check out the live animated tutorial: https://docs.datomic.com/cloud/livetutorial/datoms.html Your Datomic database consists of datoms. What are Datoms?