well yeah, there is a reason why graphql gets called 'sql for web services' after all. but I wasn't trying to draw a parallel between implementations... while

well yeah, there is a reason why graphql gets called 'sql for web services' after all. but I wasn't trying to draw a parallel between implementations... while you're obviously right that the implementation and the way you actually interface with GraphQL is very different from REST, just like that differed from SOAP, its nonetheless the same use-case. They're all communication protocols between different software components.