5 ms·

Uh, main feature of graphql is a graph cache and graph model itself. It has nothing to do with HTTP2.

by ex3ndr 7y ago

drew-y 7y ago
That's basically what the article says though. The connection to HTTP2 is that they both try and minimize the amount of requests made to a server. The author is just pointing out that GraphQL has more to offer than reduced requests.
- bityard 7y ago
  Then it was a fairly useless question to ask to begin with.
- Cshelton 7y ago
  Making a request to the server is completely different than opening a new connection. HTTP/2 lets you use an already opened connection, if applicable. Thus it is able to bypass making a handshake/etc. for every request made as well. Making a request however will still have to traverse the network irregardless. GraphQL gives you a query language to tell the server what you want in a single request. So if it is your first request to server, and a new connection needs to be opened, HTTP/2 is irrelevant. Basically, HTTP/2 and GraphQL have NOTHING to do with each other.
  - drew-y 7y ago
    That's not the point I was trying to make. I agree they are essentially unrelated. But they do both try to reduce requests made. From the article: > Not only that, but HTTP/2 has a new concept called Server Push. Without going into too much detail, server push allows servers to preemptively send responses before the client requests them.
  - ClumsyPilot 7y ago
    Even in Http 1.1 you can keep the connection open, you dont need to re-negotiate tls and friends for every request. https://en.m.wikipedia.org/wiki/HTTP_persistent_connection https://en.m.wikipedia.org/wiki/HTTP_persistent_connection
deckard1 7y ago
GraphQL has nothing to do with graphs and caching GraphQL is an exercise in masochism. And it's not even a query language in the sense of SQL. It's just about the worst named tech we currently use, IMO.
- hn_throwaway_99 7y ago
  Yes, calling it a "QL" was a huge, huge mistake, judging by the amount of comments on HN and elsewhere asking questions that are clearly influenced by an understanding of SQL but are basically non-sequiturs in the world of GraphQL (e.g. "How do you do AND joins with GraphQL?"). I admit, I didn't read the article, but even it seems like (mostly) a non-sequitur to me based on the title. Minimizing network requests is one teeny part of why I like GraphQL, and do say "we don't need it because HTTP2" is completely absurd.

Uh, main feature of graphql is a graph cache and graph model itself. It has nothing to do with HTTP2.

by ex3ndr 7y ago

Uh, main feature of graphql is a graph cache and graph model itself. It has nothing to do with HTTP2.

That's basically what the article says though. The connection to HTTP2 is that they both try and minimize the amount of requests made to a server. The author is just pointing out that GraphQL has more to offer than reduced requests.

bityard 7y ago
Then it was a fairly useless question to ask to begin with.
Cshelton 7y ago
Making a request to the server is completely different than opening a new connection. HTTP/2 lets you use an already opened connection, if applicable. Thus it is able to bypass making a handshake/etc. for every request made as well. Making a request however will still have to traverse the network irregardless. GraphQL gives you a query language to tell the server what you want in a single request. So if it is your first request to server, and a new connection needs to be opened, HTTP/2 is irrelevant. Basically, HTTP/2 and GraphQL have NOTHING to do with each other.
- drew-y 7y ago
  That's not the point I was trying to make. I agree they are essentially unrelated. But they do both try to reduce requests made. From the article: > Not only that, but HTTP/2 has a new concept called Server Push. Without going into too much detail, server push allows servers to preemptively send responses before the client requests them.
- ClumsyPilot 7y ago
  Even in Http 1.1 you can keep the connection open, you dont need to re-negotiate tls and friends for every request. https://en.m.wikipedia.org/wiki/HTTP_persistent_connection https://en.m.wikipedia.org/wiki/HTTP_persistent_connection

deckard1 7y ago

GraphQL has nothing to do with graphs and caching GraphQL is an exercise in masochism. And it's not even a query language in the sense of SQL. It's just about the worst named tech we currently use, IMO.

hn_throwaway_99 7y ago
Yes, calling it a "QL" was a huge, huge mistake, judging by the amount of comments on HN and elsewhere asking questions that are clearly influenced by an understanding of SQL but are basically non-sequiturs in the world of GraphQL (e.g. "How do you do AND joins with GraphQL?"). I admit, I didn't read the article, but even it seems like (mostly) a non-sequitur to me based on the title. Minimizing network requests is one teeny part of why I like GraphQL, and do say "we don't need it because HTTP2" is completely absurd.