News for hackers. Stuff that matters.

A comment on REST and GraphQL really aren't that different. Parent comment

Re:REST and GraphQL really aren't that different by jmull on Wednesday January 30, 2019 @03:20PM (#19039017)
No, you can batch requests.
[ Parent | on HN ]
Re:REST and GraphQL really aren't that different by wsy on Wednesday January 30, 2019 @04:00PM (#19039421)
The question was not about batching, it was about join queries over more than one resource type.
[ Parent | on HN ]
Re:REST and GraphQL really aren't that different by jmull on Wednesday January 30, 2019 @05:19PM (#19040188)
I guess I should be more clear...

batch means you can do things like combine these:

GET /serviceRoot/Airports GET /serviceRoot/People

into one request (and get the results in one response)

I believe that's what the poster was asking.

Here's a link to a different example from the OData site: https://www.odata.org/getting-started/advanced-tutorial/#bat...

You're using the word "join". I'm not sure if you meant that in a relational sense or not. If yes, then maybe you're wondering if you can get airports with their related people, or people with their related airports in one request with OData. Again, the answer is yes.

[ Parent | on HN ]
Re:REST and GraphQL really aren't that different by wsy on Thursday January 31, 2019 @02:55AM (#19043215)
Thanks for the explanation!
[ Parent | on HN ]
Re:REST and GraphQL really aren't that different by jmull on Thursday January 31, 2019 @08:28AM (#19044526)
No problem... I realize my initial answer was pretty useless. "batch" has a specific meaning in Odata but of course you wouldn't know that unless you already knew Odata.
[ Parent | on HN ]