[–] th5 4y ago ↗ As a GraphQL consumer I rather enjoy using it over Rest. I always found myself making feature requests to backend teams before. Not anymore.Maybe less true now, but it seemed like when products had public APIs in rest, they were different endpoints than what their own internal teams used.Whereas with Gql it seems like internal and public frontend people used the exact same endpoints, which gave the public apis more power.In this thread below, it seems like a lot of people on HN don’t like GQL.https://news.ycombinator.com/item?id=31284846 [–] nesarkvechnep 4y ago ↗ Have you used an actual REST API? Cacheable, making use of hypermedia. It’s much more scalable than GraphQL.
[–] nesarkvechnep 4y ago ↗ Have you used an actual REST API? Cacheable, making use of hypermedia. It’s much more scalable than GraphQL.
2 comments
[ 4.2 ms ] story [ 12.5 ms ] threadMaybe less true now, but it seemed like when products had public APIs in rest, they were different endpoints than what their own internal teams used.
Whereas with Gql it seems like internal and public frontend people used the exact same endpoints, which gave the public apis more power.
In this thread below, it seems like a lot of people on HN don’t like GQL.
https://news.ycombinator.com/item?id=31284846