3 ms·
are you saying that graph databases suffer scalability issues or are you saying relational databases used as graph databases suffer scalability issues? I've do
by sethammons 2y ago
are you saying that graph databases suffer scalability issues or are you saying relational databases used as graph databases suffer scalability issues?
I've done some high scale stuff off mysql with 10s of billions of operations a day across sharded clusters with some nodes holding terabytes of data -- fks, triggers, cascading deletes and such tended to be too expensive. I've not had the opportunity to use something like neo4j, which supposedly has a great horizontal scaling story.
edit: not that my downvoters will see, but, seriously? I'm asking a question to understand if I'm following. What are you downvoting? And yes, I've heard you are not supposed to question downvotes; I'm honestly perplexed.
- PeterCorless 2y agoThe best scalability I knew about was JanusGraph running on ScyllaDB. You can also run JanusGraph on Cassandra, which is horizontally scalable. ScyllaDB will be more performant and vertically scalable. • Docs: https://docs.janusgraph.org/storage-backend/scylladb/ https://docs.janusgraph.org/storage-backend/scylladb/ • Detailed use case: https://www.scylladb.com/2019/05/14/powering-a-graph-data-system-with-scylla-janusgraph/ https://www.scylladb.com/2019/05/14/powering-a-graph-data-sy... • Video: https://www.youtube.com/watch?v=7WZyVUTwYJ4 https://www.youtube.com/watch?v=7WZyVUTwYJ4 Note this was a few years ago. I haven't seen a TigerGraph vs. JanusGraph head-to-head. The TigerGraph people are pretty sharp. If anyone has deeper knowledge would love to see comparative benchmarks. Both JanusGraph and TigerGraph are rated about the same in terms of popularity on DB-engines.com (between 100-150 rankings). Neo4j is still far more popular/well-known, at rank #21 this past month. But there are other options you can explore.