Ask HN: What graph database you use and why? Any alternatives you had? |
Ask HN: What graph database you use and why? Any alternatives you had? |
I also used ArangoDB, back then it was a lot more stable for bulk loading than Dgraph but today I believe they're on par — Arango is multi-model which can be at times easier to reason about whilst Dgraph is a more graph-native database.
I never liked Neo4J as — back then — the horizontal scaling was impossible or extremely difficult to achieve.
End result, though... We moved everything back to Postgres and prefer to use recursive queries and metadata to query more efficiently.
I love graph database and the dream they sell, but it's just not worth it for a small entity like ours. Takes too much time dealing alphas, nodes, rebalancing shards, and so on.
But otherwise, check these two are they were great if it weren't for fleet management.
But graph database is all about how complex query or relations are between table or schema and how big are your data in your project.
Glad to hear that PostgreSQL satisfies your need. If you're looking to build a new project that requires complex query or relations, definitely give Slash a try. :)