3 ms·
GraphQL is more future proof than rest. Rest is tied to HTTP forever - GraphQL can be separated, easily. Rest communicates inputs and outputs in too many ways
by coding123 3y ago
GraphQL is more future proof than rest.
Rest is tied to HTTP forever - GraphQL can be separated, easily.
Rest communicates inputs and outputs in too many ways for my liking any more:
headers, paths, bodies, query params, and dare I say method.
One complaint for GQL is that potentially they had a chance to standardize paging, filtering, etc... instead every schema is customized.
I guess we'll have to create a new standard at some point. We'll never get this shit right.
- anttiviljami 3y agoI don’t really agree GraphQL is somehow more ”future proof” because it doesn’t use as many HTTP features. It’s not like HTTP is going to go away in a while. I find that AsyncAPI is a nice extension of OpenAPI/REST ideas if you need to go beyond request / response.
- mdaniel 3y agoIf I'm understanding coding123's comment correctly, I think AsyncAPI would need to be extended to allow specifying a GraphQL schema and not just a JSON schema as the message payload and (I guess implied?) response types