Hmm, Dgraph does seem promising. I also looked at ArangoDB, and it seems damn nice for a direct transition from MongoDB, since I'm more used to JSON storage. Neo4j is commercial for enterprise and requires learning Cypher queries, and the same goes for ArangoDB.
Neo4j does seem well supported and popular, any issues I have should get resolved.
OrientDB, on the other hand, is free to use but does seem buggy, and some online content does point to the fact that using it in production may fail.
So finally, I think I will have to decide between using OrientDB and ArangoDB. What are your opinions on this?
Just came across this post right now. What did you end up using finally?
I used Arango at my previous workplace to build a "Suggested Friends" feature. Graph queries are a pleasure to write using Arango's Query Language. The database was very performant for our user base of 1 million with around 400 edges per user. We were able to run it on a single instance with 8 GB RAM. It out-performed our previous Postgres-based solution by almost 15 times and reduced a huge Redis instance which we had needed for caching results.
Woah. Nice. I ended up with using Postgres and graphql, although I'm not working on the project anymore. The consultant was hell bent on using a cloud managed database such as RDS, and we had to use postgres.
Hmm, the app is more waterfall staged, as in, the deployment will only be taken care of at the end, the MVP is when the entire product development is done.
I'm not sure I should commit to a cloud managed database, while in development, cause if later the requirements change it might load up the work.
Will definitely have a good look at the open-source options before proceeding, thanks!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hmm, Dgraph does seem promising. I also looked at ArangoDB, and it seems damn nice for a direct transition from MongoDB, since I'm more used to JSON storage. Neo4j is commercial for enterprise and requires learning Cypher queries, and the same goes for ArangoDB.
Neo4j does seem well supported and popular, any issues I have should get resolved.
OrientDB, on the other hand, is free to use but does seem buggy, and some online content does point to the fact that using it in production may fail.
So finally, I think I will have to decide between using OrientDB and ArangoDB. What are your opinions on this?
Just came across this post right now. What did you end up using finally?
I used Arango at my previous workplace to build a "Suggested Friends" feature. Graph queries are a pleasure to write using Arango's Query Language. The database was very performant for our user base of 1 million with around 400 edges per user. We were able to run it on a single instance with 8 GB RAM. It out-performed our previous Postgres-based solution by almost 15 times and reduced a huge Redis instance which we had needed for caching results.
Woah. Nice. I ended up with using Postgres and graphql, although I'm not working on the project anymore. The consultant was hell bent on using a cloud managed database such as RDS, and we had to use postgres.
That is a shame, the devs will have a hard time scaling and querying 4+ deep relationships.
I was in the opposite situation a few months back, as a consultant I recommended a Graph database for a similar project and they ended up using a SQL.
You should probably go through a second phase of research and test them before you commit to one of them.
Managed options could be AWS Neptune and Azure Cosmos DB.
For the opensource options try also to go through their github and see how active they are and what kind of issue tickets they have open.
Hmm, the app is more waterfall staged, as in, the deployment will only be taken care of at the end, the MVP is when the entire product development is done.
I'm not sure I should commit to a cloud managed database, while in development, cause if later the requirements change it might load up the work.
Will definitely have a good look at the open-source options before proceeding, thanks!