News for hackers. Stuff that matters.
Re:Thinking in Datomic by jerf on Sunday July 08, 2012 @07:47PM (#4216094)
There have been numerous triple stores. Mozilla/Firefox even used one as its core backend for a while before ripping it out and replacing it with SQLite. Why do you think those failed, and how is Datomic going to avoid the same failures?

That is, I've seen this pitched as the solution to all our data woes numerous times now, why is this time different?

Re:Thinking in Datomic by mtrimpe on Sunday July 08, 2012 @07:54PM (#4216108)
It's not a triple store. It's closer to an OODBMS focused on persisting large object graphs with an immutable append-only datastructure, thus maintaining full history and being quite scalable with a single-writer many-reader configuration.
Re:Thinking in Datomic by pelle on Sunday July 08, 2012 @08:02PM (#4216122)
It is actually implemented more like a triple store than an oodbms. Just with time added as a 4th parameter.

Their Entity class makes it feel a bit like an oodbms though in that it kind of acts like a hash map.

Re:Thinking in Datomic by mtrimpe on Monday July 09, 2012 @09:27AM (#4218012)
Could you explain how it's more like a triple store with a time parameter?

My previous explanation already papered over a ton of fundamental differences in order to make a somewhat understandable generalization, but I can't make the jump to triple-store from my understanding of Datomic.

I basically see it as "just a single-writer many-reader distributed fully persistent data-structure."

Re:Thinking in Datomic by jerf on Monday July 09, 2012 @11:01AM (#4218483)
I'm sort of sorry to turn this around on you, because it's generally poor form, but given the contents of the linked article which describes Datomic exclusively in the form of timestamped triples, can you explain how it's not a triple store?

If it's because you store objects as many triples with the same subject and different adjectives... err, well, yes, that's how you store objects in a triple store. Not remotely new, and still subject to my initial question.

Re:Thinking in Datomic by mtrimpe on Monday July 09, 2012 @11:44AM (#4218687)
The article leads people to confuse the chosen view (triples) with the model (versioned object graph.)

The main difference is that in Datomic the timestamps don't identify a single fact but the entire object graph at that point in time.

To make an analogy; saying that Datomic is just a triple store is about the same as saying that git is just a store for lists of diffs.

Re:Thinking in Datomic by irickt on Tuesday July 10, 2012 @12:15PM (#4224536)
Triples are a simple data model that can be used for web-like graphs, relational tables, and hierarchical hashes. This is needed irrespective of Datomic's prospects. Just look at the the current massive adoption of linked data. http://news.ycombinator.com/item?id=3983179