4 ms·
I also don't see many valid use cases for graph databases.
by tschellenbach 5y ago
I also don't see many valid use cases for graph databases.
- freewilly1040 5y agoMarketing and fraud detection are pretty valid imo. Just inherently hard to scale. I do think there's a valid question of how useful n-hop queries are for an N that is greater than 2 or 3.
- tejtm 5y agoHave you tried getting grants promising they will deliver? </s>
- alexott 5y agoThere 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 5y ago2-3 hops (JOINs) is well within RDBMS territory, no?
- freewilly1040 5y agoYes. But it’s not a very exciting solution so people keep trying graph db’s.
- rektide 5y ago> I also don't see many valid use cases for graph databases. It's the most general purpose means I can see to model entities. I can't see many invalid uses.
- jshen 5y agoThey are great for data exploration, data science, analytics, etc. I would NOT put one as a dependency on a user experience though.