Well, using blueprints or not (or maybe we should start looking at tinkerpop3
which merges blueprints, gremlin and all other tinkerpop projects into 1 lib),
the main advantage of using Titan is the shared storage with metrics.
I am a little bit afraid of committing to using something that will quite
likely just slowly die.
On Wednesday, February 04, 2015 12:46:37 Jiri Kremser wrote:
Hi,
In my opinion we can still use the Blueprints API, because there are
numerous implementations out there
https://github.com/tinkerpop/blueprints/wiki
including neo4j (gpl), Mongo, OrientDB and possibly jdbc as a fallback (or
even start for mvp). If we pick something Blueprints compliant, we get the
bunch of graph algorithms for free:
https://github.com/tinkerpop/furnace/wiki
To be clear, titan will be still open-source, but without core developers, I
guess, they will give it to the apache incubator.
more info about the situation here:
https://groups.google.com/forum/#!topic/aureliusgraphs/WtU6om8CtqI
and here:
https://groups.google.com/forum/#!topic/aureliusgraphs/c07WEdH-epY
jk
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev