News for hackers. Stuff that matters.
Re:Migrating to GraphQL: A Practical Assessment by atombender on Thursday July 04, 2019 @09:34PM (#20359262)
> The required POSTs cannot be easily (if at all?) cached

GraphQL allows queries to be performed with GET:

  http://example.com/graphql?query=query{user{id}}
You want to use POST for mutations, but read queries can be run through GET and cached just like REST. There's literally no difference -- it's HTTP, after all.
Re:Migrating to GraphQL: A Practical Assessment by lwansbrough on Thursday July 04, 2019 @11:20PM (#20359577)
There is a difference. When "everybody" has a unique query, there's no cache.
Re:Migrating to GraphQL: A Practical Assessment by alexchamberlain on Friday July 05, 2019 @02:42AM (#20360358)
In practice, doesn't everyone run the same query in Production? If variables are being used, they're the same degrees of freedom that rest had anyway, right?