I’d like to suggest a 4th reason for using GraphQL. Reactive single file component UIs. If you are building your project with a reactive UI library like React or VueJS and are using single file components, being able to define your data with queries within your components is a huge code reuse win. I can’t believe this important advantage is so often missed in such articles.
The other advantage that GraphQL has over REST is the fact it is a single specification, whereas REST is full of different standards. REST is ubiquitous, but it isn’t standardized. Just look at the replies here and people interjecting, “what about OData”, “what about this”, “what about that?” If REST had a single specification, and people would have circled around that single spec to improve it over the past 15 years, we probably wouldn’t be needing a GraphQL solution at all.
Just my 2 cents!
Scott
