Personally I think the mistake is to see it as a layer on top of HTTP, in any sense other than as a hack to make it work with web browsers (using POST /graphql

Personally I think the mistake is to see it as a layer on top of HTTP, in any sense other than as a hack to make it work with web browsers (using POST /graphql as a poor man's plain old IP address or hostname). In conceptual terms, it's clearly an alternative to HTTP, so it's not a surprise that it collapses all of HTTP's expressive power into the singularity that is POST /graphql. It's interesting to imagine a web browser which truly did use GraphQL as a first-class query language comparable to SQL, with markup separated into another protocol altogether (HTTP GET, or an equivalent). I wonder what the future of web browsers looks like, and for how long we can continue simply by monkeypatching the HTTP resource model. Google's herculean efforts to adapt their crawler to the new de facto model, exemplified by SPAs, are interesting in what they reveal: https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/34736.pdf https://static.googleusercontent.com/media/research.google.c...