graph database

[unidesigner]

in the long term, we might want to move to a graph database representation of the annotation domain. with our current datamodel, that will be basically exporting the class_instance and class_instance_class_instance tables.

bio4j has a nice toolstack http://blog.bio4j.com/ and it uses neo4j.

there is a nice integration of neo4j python bindings with django in the works: https://github.com/scholrly/neo4django

[unidesigner]

http://bulbflow.com/

[unidesigner]

test http://dydra.com/

[unidesigner]

http://css.dzone.com/articles/introducing-bulbs-python

[unidesigner]

http://www.infinitegraph.com/

[unidesigner]

http://www.datomic.com/

[unidesigner]

https://github.com/thinkaurelius/titan/wiki

[unidesigner]

https://speakerdeck.com/u/okram/p/titan-the-rise-of-big-graph-data

[unidesigner]

http://www.odbms.org/blog/2012/08/on-big-graph-data/