> 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.
Here is one of the better explanations I have seen:
http://www.flyingmachinestudios.com/programming/datomic-for-...
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.
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.
"Declarative power" = among other things, datalog queries. SQL is also relatively declarative. Datomic has the benefit of declaring queries as data, not as munged strings.
"Facts are never forgotten or overwritten" = as the world changes, add a new record at a new timestamp. Traditional relational dbs modify the old record destroying previous values. The database notion of time (series of transactions) is made explicit and available as part of the query (query the db at a particular point in time or even join databases from different points in time).
For any others that are wondering, "Explain Like I'm 5"
And Datomic has been discussed in detail here...
* Rich Hickey on Datomic: Datalog, Databases, Persistent Data Structures (http://news.ycombinator.com/item?id=3797272)
* Rich Hickey on Datomic, CAP and ACID (http://news.ycombinator.com/item?id=5093037)
* The Architecture of Datomic (https://news.ycombinator.com/item?id=4732524)
* Datomic Free Edition (http://news.ycombinator.com/item?id=4286121)
* Thinking in Datomic (https://news.ycombinator.com/item?id=4215765)
* Datomic: Can Simple be also Fast? (https://news.ycombinator.com/item?id=6426362)
Docs: http://docs.datomic.com
UPDATE: Jernau gives a great practical overview in his screencast (https://www.youtube.com/watch?v=ao7xEwCjrWQ) on building a basic app with Datomic, Clojure, and Light Table.
Also see "Learn Datalog Today" (http://www.learndatalogtoday.org) for an interactive Datalog tutorial.
I'm sure it's a wonderful app, but its first-impression presentation doesn't tell me what it is I'm looking at. And as such, I'm just going to click away and find something else.
"Code can never corrupt data again"
Couple of scenarios:
1) A runaway data generator. Somehow you end up confusing milliseconds with seconds and now you start logging 1000x more data than you intended, you leave for the weekend and find your storage is full of junk
2) Sensitive data. Felix has just inserted all the passwords and credit card numbers in the database.
I'll pretend I don't know who Hickey is and just say that I expect a lot of stupid decisions can be made when coming up with "a completely new way of looking or storing data". Some databases (cough...cough...starts with M) shipped their database product with unacknowledged writes as the default, oops. Everyone can make a database.
Now let's dig deeper. The reason I asked what I asked it because given the architecture of Datomic and the claims made, that corner case (excision) would not be trivial or and would have to be implemented as a hack on the side. That is why I asked. In some databases it is easier to do, in that architecture it is hard.
> or only when it's talented programmers working on a database?
Who are these talented programmers? Are you a talented programmer?
Right now, the impression I get is, "ooh, because Rich Hickey..."
Could anyone share anecdotes to the counter ?
Granted I'm coming from a do-it-myself green-field project, but the things that Datomic's structure and design opens up for my personal project mean that me, a one man show, can far more easily go toe to toe with the big guys with massive teams to design and deploy their apps and databases.
Potential is what I see, and it's far more than I've seen with just about any other technology that I can think of. I really think Datomic is a game changer, at least for the few awake enough to see it.
This isn't intended to bag on triple stores - I work on them for a living - or Datomic specifically. Triple stores are very useful and in many ways liberating to work with, but they do present challenges when querying over lots of data.
learning the value of functional style took ages for me to grok, but it's been one of the biggest values ever.
i find it a little ironic considering one of the first and best talks i've seen from hickey is 'simple made easy'. you'd likely learn a lot from a watch of that, or perhaps more detail about datomic in any of the talks on datomic.
> Datomic is a database of flexible, time-based facts, supporting queries and joins, with elastic scalability, and ACID transactions. > Datomic can leverage highly-available, distributed storage services, and puts declarative power into the hands of application developers.
What does that even mean? I'm pretty good at databases, and I know what transactions and queries and joins and stuff, but this explanation does a pretty poor job of explaining what Datatomic is and why I should use it.
What's a "time-based fact"? What does putting "declarative power in the hands of application developers" mean? Don't all databases support queries? Don't most relational databases support joins and transactions?
It just seems like a buzz-word filled fluff phrase that says "Datatomic is a database," but I don't know why I would use it over, say, MySQL or Mongo or whatever.
I had to go to Cognitect's site (http://cognitect.com/datomic) to get a better explanation:
>Datomic is built on immutable data; facts are never forgotten or overwritten. This means complete auditability is built in from the start - including the transactions that modify your database. And because Datomic is built on immutable data, you can explore possible future scenarios by issuing transactions against a database and decide to commit them only after verifying the results.
Ok, that makes a little more sense, but it's still not clear what differentiates this from other database systems.
I'm not affiliated with them at all, but I think SiftScience.com does a great job of explaining their product simply and efficiently: https://siftscience.com/
> Fight Fraud with Machine Learning > Sift Science monitors your site's traffic in real time and alerts you instantly to fraudulent activity.
Simply detects fraud. Done.
Or EasyPost.com:
> Shipping for developers > EasyPost allows you to integrate shipping APIs into any application in minutes.
Don't just spit buzz words and technical terms at me. Tell me what it does.
> Datomic is a database that, among other things, specializes in tracking data over time, allowing you to test a transaction before saving the data. True accountability from the beginning!
Probably not even accurate (again, I don't understand Datomic's premise), but that sounds more explanatory than their current buzz word-filled blurb.
To any startups watching: have something on your front page that is an ELI5 description of your product.