Talk:GraphQL

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

don't understand

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)[reply]

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)[reply]

Sources

5 sources out of 18 are unreliable. I wonder how does this even meet WP:GNG... AXONOV (talk) ⚑ 20:00, 5 August 2021 (UTC)[reply]

What problem is GraphQL designed to solve?

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)[reply]