I'm not experienced (just a hobby programmer), but I can't think of any use case where it couldn't be done better with a graph.
But I have previously found the tiniest bit of discussion here: https://news.ycombinator.com/item?id=2785663 On Friday, 31 July 2015 07:45:05 UTC+8, Eric24 wrote: > > I'm learning more and more about OrientDB and graph databases every day. > One question that I've seen lots of conflicting comments about across the > Internet is use-cases where SQL/RDBMS are preferred over a graph database > (most of what I've seen uses Neo4j as their graph database "foil"). I'm an > expert-level SQL developer (with 20+ years experience designing RDBMS > databases, in the past 15 years or so primarily using MS SQL), so I have a > very firm grasp of what is possible there and what limitations exist, but > I'm only getting started on graph databases (and specifically OrientDB, > which so far, I'm very impressed and intrigued by). So I'd love to hear > some feedback from some experienced OrientDB users (and authors) on > use-cases that you would recommend be done using RDBMS instead of graph > (and specifically OrientDB), and why. > --Eric > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
