"On the other hand, when fetching for the same data with REST we would end up with multiple REST roundtrips"
IMO, anything graphql does, rest can and vice versa. But when you're doing more REST things on a graphql api, then you should just go REST.
Many rest frameworks support "data" or property filtering.
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.
"On the other hand, when fetching for the same data with REST we would end up with multiple REST roundtrips"
IMO, anything graphql does, rest can and vice versa. But when you're doing more REST things on a graphql api, then you should just go REST.
Many rest frameworks support "data" or property filtering.