YUP, HyperGraphDB supports JSON document storage (*), just like MongoDB, is transactional, unlike MongoDB which isn't, and the documents are actually graphs, therefore all interlinked through the graph structure transparently, so you can match up any structural patterns.

http://java.dzone.com/articles/you-definitely-shouldnt-use?mz=36885-nosql

(*) http://hypergraphdb.org/learn?page=Json&project=hypergraphdb

This paper develops an extension to SPARQL supporting graph paths and "folders" (essentially subgraphs) called FPSPARQL, and then does some common practical queries comparing performance with SPARQL and HyperGraphDB circa 2010. It would be interesting to run their performance tests with the latest version of HyperGraphDB, in particular using the subgraph implementation.

http://arxiv.org/abs/1211.5817

#hypergraphdb   #nosq   #programming   #semanticweb

eValhalla 2nd iteration - basic user management with login and registration as well as a simple generic CRUD data service. #hypergraphdb   #nosql   #angularjs   #restlet  #scala #json
http://kobrix.blogspot.com/2012/10/evalhalla-setup.html

http://scalahypergraph.blogspot.de/2012/11/scala-closures-as-hypergraphdb.html

http://blog.opencog.org/2013/03/24/why-hypergraphs/

A few Scala hacks to make it easier to work with the HyperGraphDB API: implicit graph object, handle dereferencing and "foreach" iterable traversals.

#hypergraphdb   #nosql #programming #scala
http://scalahypergraph.blogspot.de/2012/12/a-shift-of-perspective-hacking.html

http://kobrix.blogspot.com/2012/11/hypergraphdb-12-final-released.html