News for hackers. Stuff that matters.

A comment on Migrating to GraphQL: A Practical Assessment. Parent comment

Re:Migrating to GraphQL: A Practical Assessment by dmitriid on Friday July 05, 2019 @03:31AM (#20360548)
> There’s a whole category of thinking you don’t have to engage in (is this POST? PUT?)

There’s a reason that category of thinking exists. But since GraphQL libs are now busy implementing caching in top of non-cacheable POST requests, this argument is lost on them.

[ Parent | on HN ]
Re:Migrating to GraphQL: A Practical Assessment by dmitryminkovsky on Friday July 05, 2019 @02:53PM (#20364843)
> There’s a reason that category of thinking exists.

What's the reason?

> But since GraphQL libs are now busy implementing caching

What are you referring to? You mean like https://github.com/graphql/dataloader ?

> in top of non-cacheable POST requests, this argument is lost on them.

I think caching/serving HTTP results is a bad paradigm. It makes sense if you're serving HTML for a content site or something like that, but doesn't make sense when you're serving an API.

[ Parent | on HN ]