[alexott]

There is a lot - customer support (aka customer 360), fraud detection, some maintenance cases, inventory, recommendations, etc. But it’s heavily dependent on requirements - what should be response time. Most of graph databases are good in fast response time, but will do it only for 2-3 hops from known start points. For many other things, graph analytics with Spark or something like could be better

[pphysch]

2-3 hops (JOINs) is well within RDBMS territory, no?

[freewilly1040]

Yes. But it’s not a very exciting solution so people keep trying graph db’s.