That's a good question.
I am referring to high no. of data points = high no. of fields / highly normalized schema.
Sorry for not being clear.
Thanks for clearing out.
It would be great if you can elaborate on the following point as well:
Remember that plain Rest API implementations are simpler
I intended to recommend GraphQL for databases that have many fields and/or relationships.
".. Since most of my services are data-heavy, I particularly like the fact that I don't need to maintain a dozen end-points".
GraphQL enables selective retrieval and that (for me) is a big plus.
Obviously I am not a good communicator :p
I would like to answer your second question in more detail and have updated the post!
Thanks for the great questions.
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.
That's a good question.
I am referring to high no. of data points = high no. of fields / highly normalized schema.
Sorry for not being clear.
Thanks for clearing out.
It would be great if you can elaborate on the following point as well:
I intended to recommend GraphQL for databases that have many fields and/or relationships.
"..
Since most of my services are data-heavy, I particularly like the fact that I don't need to maintain a dozen end-points".
GraphQL enables selective retrieval and that (for me) is a big plus.
Obviously I am not a good communicator :p
I would like to answer your second question in more detail and have updated the post!
Thanks for the great questions.