REST vs. GraphQL – A search for evidence on which is better

Re:REST vs. GraphQL – A search for evidence on which is better by plif on Wednesday December 16, 2020 @01:09AM (#25439615)

I don't think #2 is that big of a deal if all requests happen async, which they should with a client side ORM, and if you're using http2.

I think the bigger problem there is how those multiple REST calls map to your data stores. Very rarely will there be clean separation of data between endpoints, and the stateless nature of REST makes it harder to optimize each call -- meaning, there will almost certainly be redundant queries.

That said, with GraphQL, your front end dev may not realize they are executing the equivalent of many REST calls, which is another problem :) I wouldn't say it's harder to optimize if you look at the application as a whole, though.

[ Parent | on HN ]

Re:REST vs. GraphQL – A search for evidence on which is better by Aeolun on Wednesday December 16, 2020 @06:30AM (#25441399)

If you cache enough, your frontend dev can call as many things as they want and it will still be more or less instant.

[ Parent | on HN ]

Re:REST vs. GraphQL – A search for evidence on which is better by virgilp on Wednesday December 16, 2020 @07:02AM (#25441602)

Some people, when confronted with a performance problem, think "I know, I'll use a cache." Now they have two problems.

(in other words: caching is complicated, and may make your systems very hard to understand & debug)

[ Parent | on HN ]