4 ms·
You're right, their description should be clearer, or have an elaboration or something. But for onlookers: > flexible Minimal, non-tabular schema > time-base
by brandonbloom 13y ago
You're right, their description should be clearer, or have an elaboration or something. But for onlookers:
> flexible
Minimal, non-tabular schema
> time-based
All historical values are preserved.
> facts
Triple store: Entity / Attribute / Value
with time:
Quad store: Entity / Attribute / Value / TIME
> supporting queries and joins
Datalog query language
> with elastic scalability
Reads are uncoordinated, so they scale horizontally
> ACID transactions.
You can trust the database won't lose stuff you write to it.
> leverage highly-available, distributed storage services
Storage engines are pluggable. You can choose backends such as filesystems, Riak, Dynamo, traditional SQL databases, etc.
> puts declarative power into the hands of application developers.
Reads occur in-process, like an embedded database. Queries, traversal, and other reads occurs locally, without network round trips.
- cordite 13y agoThere's definitely a lot more to ACID than the part you mention, which fulfills the D or Durability aspect. Though to any competent database engineer, they already know what ACID is. The videos on datomic's website help clarify the understanding, but that isn't as accessible as well written text.
- brandonbloom 13y ago> (map eli5 (acronym-expand "ACID")) Atomic: Transactions are all-or-nothing. You never see half of a transaction. You either get the world before the transaction, or after it. Consistent: The before and after worlds are always valid, never corrupt. Isolated: From the outside, it appears that transactions occur one-after-another, never overlapping in time. In Datomic, this is actually the case: Transactions are fully serialized. Durability: If a transaction succeeds, you can be confident that the consistent "after" world is safely on disk.
- Jemaclus 13y agoThanks for breaking down the buzzwords into something understandable!
- deleted 13y ago[deleted]
- tony_landis 13y agoGenerally speaking, five year olds should not be choosing databases for anything critical. But I agree that Datomic and company can do better with their marketing and general product description. Here is one of the better explanations I have seen: http://www.flyingmachinestudios.com/programming/datomic-for-five-year-olds/ http://www.flyingmachinestudios.com/programming/datomic-for-...