REST and GraphQL really aren't that different

Re:REST and GraphQL really aren't that different by napoleond on Wednesday January 30, 2019 @03:07PM (#19038864)

AFAIK, oData only lets you request a single entity type at a time, doesn't it? For example, in the example you provided, would it be possible to fetch a collection of People and Airports as part of the same request? What would that request look like?

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by ako on Wednesday January 30, 2019 @04:17PM (#19039603)

You can include associated entities by using expand, e.g. order with orderlines. See: https://www.odata.org/getting-started/basic-tutorial/#expand

The oData contract, $metadata, describes an entire domain model, including associations between entities. You can use expand to join entities over these associations.

You can request multiple queries in one http operation using batch requests: https://www.odata.org/getting-started/advanced-tutorial/#bat...

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by jbreiding on Wednesday January 30, 2019 @03:29PM (#19039094)

No, you can query a collection of these entities and get back the resulting set with pagination.

[ Parent | on HN ]

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 ]