DEV Community

loading...

Discussion on: Deciding a database architecture for a Social Networking use-case?

Collapse
rrampage profile image
Raunak Ramakrishnan • Edited

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.

Thread Thread
presto412 profile image
Priyansh Jain Author

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.

Thread Thread
bgadrian profile image
Adrian B.G.

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.