# GraphQL at Braintree

<https://www.braintreepayments.com/blog/graphql-at-braintree/>

- Host: [braintreepayments.com](https://links.thingelstad.xyz/hosts/braintreepayments.com/)
- Saved: March 20, 2018 (2018-03-21T02:42:19Z)
- Record: https://links.thingelstad.xyz/links/decf8811f3c5/
- JSON: https://links.thingelstad.xyz/links/decf8811f3c5.json

## What Jamie wrote

Interesting overview of how Braintree evaluated and ultimately chose to use GraphQL for their published API's.

> The previously mentioned benefits would be enough to make a reasonable case for adopting GraphQL on their own. Our biggest surprise, however, was how perfectly suited GraphQL is for powering an orchestration layer.
> 
> GraphQL forces you to cleanly separate logic for retrieving data from logic that composes this data and presents it to the user. You write code for the former and your GraphQL framework handles the latter.

Also highlights challenges they had. Good read.

## Facts

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

## Appears in

- [WT46: Weekly Thing #46 / Mar 24, 2018](https://weekly.thingelstad.com/archive/46/), Links 📌

## Saved the same week

- [A Day in the Life of MARLON BUNDO](https://links.thingelstad.xyz/links/793ad8f2a682/) (betterbundobook.com, March 20, 2018)
- [Functions | Netlify](https://links.thingelstad.xyz/links/233bb9ebefd6/) (netlify.com, March 20, 2018)
- [D3 Graph Theory](https://links.thingelstad.xyz/links/80a9030c5de4/) (mrpandey.github.io, March 20, 2018)
- [Revealed: 50 million Facebook profiles harvested for Cambridge Analytica in major data breach | News | The Guardian](https://links.thingelstad.xyz/links/65bea5ddf08e/) (theguardian.com, March 20, 2018)
- [#deletefacebook | TechCrunch](https://links.thingelstad.xyz/links/e973781a3e9f/) (techcrunch.com, March 20, 2018)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://www.braintreepayments.com/blog/graphql-at-braintree/