3 ms·
If I were doing a lot of graph specific stuff, where it was crucial to store the graph itself, I'd definitely go with a pure graphdb over trying to shoe-horn it
by mindcrime 10y ago
If I were doing a lot of graph specific stuff, where it was crucial to store the graph itself, I'd definitely go with a pure graphdb over trying to shoe-horn it into a relational db, or even Cassandra. It's hard to give a real precise answer without more info, but Neo4J is probably a good starting point unless your requirements are real specific in some way that isn't compatible with Neo4J.
You should probably also ask if you really need a graph database or if you just need to use a graph processing engine (like Giraph) to perform graph operations on data that can be extracted from elsewhere.