Since one of the talks got canceled the organisers of the Graph Devroom at Fosdem used the opportunity to make a public discussions with all the developers to talk about some future trends in graph processing. I really liked the idea but unfortunately the discussion wasn’t really kicking off well. I guess for a discussion like this people have to prepared in a better way.
- Topics were Blueprints (a common graph accass api) created by Marko Rodriguez as
- Problem of real time graph processing
- Benchmarking issues (we need standards for benchmarking).
- A guy from OrientDB raised the question weather Graph databases should really have ACID transaction?
- Max De Marzi raised the question about are graphs changing while processing or are they rather static?
- Achim Pointed out that Relational databases are actually a special case of Graph databases. He demands vendors to generalize more and consolidate the technologies…
The room was not as full as the talks before but sill half of the seats have been filled as you can see on this short video:
My thoughts on acid discussion
I think that the ACID question was interesting. Alistair from neo4j gave a fine response to this saying that it clearly depends on the usecase and the kind of transactions that you really need. He compared to the relational data base world where you might have the option of switching ACID off.
He says that “in neo4j you cannot shut off ACID as neo4j believes that for most of their customers this is the best choice. But he admits that there are use cases where you migh want to shutoff ACID.
Changing graphs vs static graphs
I think that this is also a very important question. On one hand we have static models like Giraph that are able to find answers on huge static graphs on the other side you have situations like graphity where you have fast fluctuation in data. Unfortunately for the later there is no technology I know of (besides hidden Facebook and Twitter and Googleplus) .