RDBMS are developed with joins in mind, but also die of the complexity involved resulting from these joins (both from developer perspective, as well resources.)
Now imagine your join to become a primary perspective to look at your data.
Then you'd see creditcard transactions (who buys what when?) or maps are better represented as a graph.
I know for example TomTom uses neo4j to validate map edits in production.
Now imagine your join to become a primary perspective to look at your data. Then you'd see creditcard transactions (who buys what when?) or maps are better represented as a graph. I know for example TomTom uses neo4j to validate map edits in production.