Show HN: Introduction to GraphQL

GraphQL is nice (we use it in the issue tracker we're building [0]) but I think some proponents get a little over zealous and make some untrue statements about traditional "REST" APIs.

Like this:

> These two classic REST flaws force REST users to always get the full payload in response & hit multiple data sources separately.

That's simply not true. Nothing stops you from building a boring old JSON-over-HTTP API that supports filtering. I've done it lots of times. Also, there's nothing that stops you from getting data from multiple sources. Anyone's who build anything with microservices does that every day.

What GraphQL does is standardize the way these things are done and by doing so allows libraries/frameworks to make doing these things incredibly convenient.

So yes, GraphQL is cool, but the rhetoric needs to be dialed down a bit.

0: https://kitemaker.co