The recent workshop on Graph Databases in Barcelona sparked an interesting debate among vendors of graph databases about how to accelerate graph database adoption.
I don’t think that debate has been resolved yet. Perhaps this post will help a bit.
Some opinions that I heard were:
- there are significant differences between the various graph database products on the market (e.g. graphs, property graphs, properties on edges or not, hypergraphs etc.). Unless they are more similar, customers will fear lock-in and not buy any of them. Here is a variation:
- relational databases only took off once there was agreement on the SQL standard among vendors. We need to cooperate to create a similar language, otherwise graph database adoption will not take off either.
- most potential users of graph databases have never heard of them. How could they use any if they don’t know they exist?
- even if possible users know of graph databases, they do not know what the use cases are because use cases and success stories have not broadly been documented.
What do you think the biggest obstacles are for graph database adoption?