3 ms·
GQL has issues like every tech does, but it feels so much more ergonomic from an api consumer point of view. Simply point Insomnia at the base url and it’ll in
by ecf 6y ago
GQL has issues like every tech does, but it feels so much more ergonomic from an api consumer point of view.
Simply point Insomnia at the base url and it’ll introspect the schema and provide typed query auto completion. No dozens of requests to different endpoints with different query parameters than can only be kept track of by having the api docs open on a second screen.
- deckard1 6y agoIt's only ergonomic if you've never done REST before. I'm not being flippant. If you're already using REST tools such as Postman and every caching tool in existence (browser, http proxy, etc. etc.) then GraphQL tossing it all out is the exact opposite of "ergonomic." The caching story in GraphQL is a joke. What the browser gives you for free with GET caching takes weeks and months of fine-tuning and tweaking and head scratching with something like Apollo. Then you'll probably try decreasing the payload size (there's a third-party solution for this), or batching requests together (guess what... there is a third-party solution for this too). The amount of tooling and implementation work GraphQL needs to get up to par with built-in REST is pretty incredible.