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.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
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.