I do believe graph databases are here to stay. However, they are overhyped right now, leading everybody to think their problem is a graph problem, just like how the hype of hadoop led everybody to believe their problem was a map reduce problem.
A good rule of thumb is whether you ever have a need to query the relations as well as the data. If you ever get to that point, you can be pretty well assured that a graph database will help you. Until then, the safer decision is to stick with a relational db for prod.
Also, check out OrientDB. I have found it to be superior in every way to Neo4j.
Comments
I do believe graph databases are here to stay. However, they are overhyped right now, leading everybody to think their problem is a graph problem, just like how the hype of hadoop led everybody to believe their problem was a map reduce problem.
A good rule of thumb is whether you ever have a need to query the relations as well as the data. If you ever get to that point, you can be pretty well assured that a graph database will help you. Until then, the safer decision is to stick with a relational db for prod.
Also, check out OrientDB. I have found it to be superior in every way to Neo4j.