Talk:GraphQL
Add topic | This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
don't understand
[edit]I'm really not trying to throw rocks at GraphQL, I'm trying to get the premise.
"allows clients to dictate what data is needed, therefore preventing excessively large amounts of data being returned"
How does allowing clients to dictate need prevent excessive usage?
I've worked at places that throw out open query patterns (e.g. OData) because it allows client side and mid tier programmers to request whatever comes into their brains.
How does this limit usage?
162.93.65.2 (talk) 12:59, 16 May 2018 (UTC)
- The purpose is not at all for the server to force its clients to limit themselves, but to allow them to get lighter responses for a route, by getting the fields they need only. JackPotte (talk) 11:51, 6 May 2020 (UTC)
Sources
[edit]5 sources out of 18 are unreliable. I wonder how does this even meet WP:GNG... AXONOV (talk) ⚑ 20:00, 5 August 2021 (UTC)
What problem is GraphQL designed to solve?
[edit]The solution is described: aggregate response data from multiple APIs.
To what problems is GraphQL the solution? Benklaasen (talk) 09:29, 9 May 2024 (UTC)