3 ms·
GraphQL is pretty different from REST and SOAP. In practice it is like exposing a very limited interpreter directly to the public internet. Instead of working
by dnomad 8y ago
GraphQL is pretty different from REST and SOAP.
In practice it is like exposing a very limited interpreter directly to the public internet. Instead of working with resources and limited verbs and hypermedia or SOAP (which is literally just documents) you allow clients to submit what are essentially programs with are then evaluated. In other words its mobile code all over again. [1]
[1] https://en.wikipedia.org/wiki/Code_mobility https://en.wikipedia.org/wiki/Code_mobility
- y4mi 8y agowell 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.