# Living APIs, and the Case for GraphQL — Brandur Leach

<https://brandur.org/graphql>

- Host: [brandur.org](https://links.thingelstad.xyz/hosts/brandur.org/)
- Saved: June 10, 2018 (2018-06-10T13:01:46Z)
- Record: https://links.thingelstad.xyz/links/0b780ab58db2/
- JSON: https://links.thingelstad.xyz/links/0b780ab58db2.json

## What Jamie wrote

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?

## Facts

- Kind: [Page](https://links.thingelstad.xyz/kinds/page/)

## Appears in

- [WT58: Weekly Thing #58 / Jun 16, 2018](https://weekly.thingelstad.com/archive/58/), Notable Links 📌

## Saved the same week

- [Interviewing is a noisy prediction problem · Erik Bernhardsson](https://links.thingelstad.xyz/links/60b43bd64286/) (erikbern.com, June 9, 2018)
- [10 weird and wonderful derailleurs – and how they changed cycling | Environment | The Guardian](https://links.thingelstad.xyz/links/68ae3d6184b2/) (theguardian.com, June 10, 2018)
- [Be a Better Scrum Master: 10 Practices to Take to Heart](https://links.thingelstad.xyz/links/382c7e33ce27/) (mountaingoatsoftware.com, June 10, 2018)
- [Coinholder Club](https://links.thingelstad.xyz/links/7482be75eebc/) (coinholder.club, June 10, 2018)
- [Management books in review – Built to Run](https://links.thingelstad.xyz/links/5c06a8faeba9/) (kimmoir.blog, June 10, 2018)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://brandur.org/graphql