I am new to these stuffs. So as I understand HTTP/2 comes with some improvements over HTTP/1.1. So how can HTTP/2 be used for data intensive request without needing to use GraphQL?
HTTP/2 is just a transport that GraphQL and other http-based protocols can use. It may reduce the overhead of round tripping and multiple concurrent connections a little, but it is no substitute for protocol design that drastically reduces or eliminates round tripping (as can GraphQL)
By data intensive I meant something where we have to make multiple requests for similar data, but not quite the same. If I understand correctly, graphql is there to help with such cases. But, I may be wrong, I am new to this.
4 comments
[ 3.5 ms ] story [ 14.1 ms ] threadCould you clarify some things?
- what do you mean by data intensive requests?
- what caused you to look into HTTP2 in the first place?
By data intensive I meant something where we have to make multiple requests for similar data, but not quite the same. If I understand correctly, graphql is there to help with such cases. But, I may be wrong, I am new to this.
Just curiosity.