Show HN: REST Alternative to GraphQL and tRPC

Re:Show HN: REST Alternative to GraphQL and tRPC by coding123 on Tuesday October 10, 2023 @10:46AM (#37832779)

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.

[ Parent | on HN ]

Re:Show HN: REST Alternative to GraphQL and tRPC by anttiviljami on Tuesday October 10, 2023 @12:40PM (#37834381)

I 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.

[ Parent | on HN ]

Re:Show HN: REST Alternative to GraphQL and tRPC by mdaniel on Tuesday October 10, 2023 @03:19PM (#37836257)

If 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

[ Parent | on HN ]