Hacker News
new
|
past
|
comments
|
ask
|
show
|
jobs
|
submit
login
brblck
on Sept 14, 2016
|
parent
|
context
|
favorite
| on:
The GitHub GraphQL API
Yup. That's something we can handle internally, under the hood to batch database requests into a single query for all edges. This problem is actually
easier
to solve in GraphQL then it is with a traditional REST API.
arianvanp
on Sept 14, 2016
[–]
Exactly, now you put the onus to solve N+1 on the serverside, instead of in the old case the client would do N+1 requests...
Guidelines
|
FAQ
|
Lists
|
API
|
Security
|
Legal
|
Apply to YC
|
Contact
Search: