I am trying to put together a short presentation a...
# orm-helpa
Arnab
05/13/2018, 4:49 PMI am trying to put together a short presentation about why people should switch to GraphQL. So far, I have been focusing on the following things:
- the power of fetching everything in one go
- avoiding over/underfetching
- self-documenting API
- strongly typed schema that helps you validate your input
- reusing existing models vs always implementing custom endpoints.
What other big wins are you missing from this list? I have decided to keep subscriptions and fragments off my list for now.
n
nikolasburk
05/13/2018, 4:50 PM
Hey Arnab, that’s already a pretty good summary. You might also take a look at this article for some inspiration: https://blog.graph.cool/top-5-reasons-to-use-graphql-b60cfa683511
nikolasburk
05/13/2018, 4:51 PM
I think composing APIs with schema stitching is another big one you might want to add
✔️ 1
a
Arnab
05/13/2018, 4:52 PMI actually considered that too but it might go over some people's heads if they have never seen graphql before.
n
nikolasburk
05/13/2018, 4:54 PM
Agreed, I think just communicating the vision on a high-level might work though. Eg. by giving an example where apps can fetch data from GitHub, Yelp and Shopify in a single query without needing to know any details about the respective APIs
nikolasburk
05/13/2018, 4:54 PM
But yeah, definitely an advanced use case.
a
Arnab
05/13/2018, 4:55 PMHm maybe
Arnab
05/13/2018, 4:55 PMI don't know if I myself can explain it in some detail, so I will have to communicate it like you said
c
cmcinroy
05/14/2018, 9:21 AM@Arnab in fact, your last bullet would make a nice segue into the composition benefit.