News for hackers. Stuff that matters.
Re:Migrating to GraphQL: A Practical Assessment by he0001 on Sunday July 07, 2019 @05:58AM (#20374380)
But that’s not reducing the complexity of the API, just the payload. If you remove the “load all users with everything in it” API the backend still needs to load all users and the filter it to reduce the payload. If the backend doesn’t have that capability graphql cannot ask for that functionality, so you still rely on the team to have implemented it.
Re:Migrating to GraphQL: A Practical Assessment by pm90 on Sunday July 07, 2019 @11:58AM (#20375709)
Don’t move the goddamn goalposts. The responses are to the specific question of reducing read api payloads which you have admitted is what it does. It’s not to reduce the complexity of the api or whatever new arbitrary goal you invent next.