News for hackers. Stuff that matters.

A comment on How GraphQL Replaces Redux. Parent comment

Re:How GraphQL Replaces Redux by wmdmark on Tuesday March 13, 2018 @02:07PM (#16578270)
That's true however at that point our API is not longer "RESTfull" and become very ad hoc. The cool thing we found with GraphQL is that the client can control the shape of the data it needs without any server side changes (assuming your schema exposes everything properly).
[ Parent | on HN ]
Re:How GraphQL Replaces Redux by sect2k on Tuesday March 13, 2018 @02:17PM (#16578386)
> The cool thing we found with GraphQL is that the client can control the shape of the data it needs without any server side changes.

This is the single biggest advantage of GraphQL and AFAIK one of the main reasons for it's conception.

[ Parent | on HN ]
Re:How GraphQL Replaces Redux by dmitriid on Tuesday March 13, 2018 @04:43PM (#16579612)
> That's true however at that point our API is not longer "RESTfull" and become very ad hoc.

So.... That's why you decide to create ad-hoch APIs using GraphQL queries instead: "the client can control the shape of the data it needs"

[ Parent | on HN ]
Re:How GraphQL Replaces Redux by nawitus on Tuesday March 13, 2018 @02:37PM (#16578592)
Why is returning say the three top comments not RESTful?
[ Parent | on HN ]
Re:How GraphQL Replaces Redux by lparry on Tuesday March 13, 2018 @04:58PM (#16579725)
Because in rest, urls are supposed to specify a resource, but now your response is a resource and some other resources too.

Not saying that being pure to rest ideology is a good thing. I think it’s a terrible fit for most applications more complex than a demo todo app

[ Parent | on HN ]
Re:How GraphQL Replaces Redux by icebraining on Tuesday March 13, 2018 @05:40PM (#16580084)
There's nothing "impure" about that. From Fielding's dissertation (emphasis mine):

"The key abstraction of information in REST is a resource. Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on."

By the way, REST is not an ideology, it's an architectural style. It defines a set of constraints, and specifies the advantages and disadvantages of applying each of them.

[ Parent | on HN ]