Living APIs, and the Case for GraphQL — Brandur Leach


34 bookmarks. First posted by theGrowingNoise june 2018.


Thoughtful reasoning for using GraphQL as your API structure of choice.

> A vanilla installation of GraphiQL is a more powerful integration tool for users than what 99% of REST providers have, and it’s available automatically, and for free.

I’m not sure if this happens in other industries, but this does seem to argue for a REST v. GraphQL. Does it have to be **versus**? It would seem likely that we could suggest REST is better for what it does, representational state transfer, and GraphQL would be best for what it does, deal with connected data?
june 2018 by thingles
It’s hard to read exactly where GraphQL stands in the APIworld right now. Available publicly since 2015, trends inAPIs aren’t obviously moving in its favor, but…
from instapaper
june 2018 by kohlmannj
It’s hard to read exactly where GraphQL stands in the API world right now. Available publicly since 2015, trends in APIs aren’t obviously moving in its favor, but not obviously moving against it either.
june 2018 by AnthonyBaker
Living APIs and the Case for GraphQL
from twitter_favs
june 2018 by rukku
It’s hard to read exactly where GraphQL stands in the APIworld right now. Available publicly since 2015, trends inAPIs aren’t obviously moving in its favor, but…
from instapaper
june 2018 by mledu