# Why use GraphQL, good and bad reasons · Honest Engineering

<https://honest.engineering/posts/why-use-graphql-good-and-bad-reasons>

- Host: [honest.engineering](https://links.thingelstad.xyz/hosts/honest.engineering/)
- Saved: August 28, 2018 (2018-08-29T04:07:02Z)
- Record: https://links.thingelstad.xyz/links/145946bb854a/
- JSON: https://links.thingelstad.xyz/links/145946bb854a.json

## What Jamie wrote

The capabilities related to **complex schemas** and **microservice orchestration** are the most compelling justifications for GraphQL. If I were doing more with mobile, I can see how the mobile use case is very helpful. I agree wholeheartedly on the assessment that REST v. GraphQL is a silly debate.

> GraphQL and REST are both very different things, GraphQL is a language and a technology, REST is an architecture pattern.

Yes.

## Facts

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

## Appears in

- [WT69: Weekly Thing #69 / Sep 1, 2018](https://weekly.thingelstad.com/archive/69/), Notable Links 📌

## Saved the same week

- [Internet chat system IRC turns thirty | University of Oulu](https://links.thingelstad.xyz/links/b5b9a75e3da1/) (oulu.fi, August 28, 2018)
- [Stop Using WhatsApp If You Care About Your Privacy](https://links.thingelstad.xyz/links/06b815e11a32/) (lifehacker.com, August 28, 2018)
- [How Facebook, Apple and Microsoft are contributing to an openly licensed map of the world – The ODI](https://links.thingelstad.xyz/links/b3eb88614c29/) (theodi.org, August 28, 2018)
- [Is It Okay to Say “Hey Guys”? - The Atlantic](https://links.thingelstad.xyz/links/9a807d499b77/) (theatlantic.com, August 28, 2018)
- [What do you believe now that you didn't five years ago? Centralized wins. Decentralized loses. - High Scalability](https://links.thingelstad.xyz/links/76348e657513/) (highscalability.com, August 28, 2018)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://honest.engineering/posts/why-use-graphql-good-and-bad-reasons