News for hackers. Stuff that matters.

A comment on The GraphQL stack: How everything fits together. Parent comment

Re:The GraphQL stack: How everything fits together by boubiyeah on Thursday November 09, 2017 @09:28AM (#15662608)
Are you talking about a single client and its server? (a.k.a backend-for-frontend). This is not a hard problem to solve when you share a single programming language, with or without graphql.

Because you can't possibly now what your API consumers use on their side.

[ Parent | on HN ]
Re:The GraphQL stack: How everything fits together by yen223 on Thursday November 09, 2017 @03:40PM (#15665703)
> Because you can't possibly now what your API consumers use on their side.

Not only do we know exactly what fields the API consumers are using, we also know the types they're expecting. We can make schema refactors fairly safely. That goes a long way towards making the codebase less brittle as a whole

[ Parent | on HN ]
Re:The GraphQL stack: How everything fits together by djmashko2 on Thursday November 09, 2017 @10:44AM (#15663314)
> Because you can't possibly now what your API consumers use on their side.

That's the best part - with GraphQL you _do_ know, since people have to ask for every single field they want.

[ Parent | on HN ]