Add graphql introduction #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| } | ||
| ``` | ||
|
|
||
| It's basically how to get GraphQL up and running on the server-side. As we can see, GraphQL is a contract that has been designed with a flexible syntax making the building of client applications easier. Also, we can see how GraphQL challenges the ReST API architecture. For instance, as we know, [a REST API typically delivers all the data a client UI might need about a resource and leaves it up to the client to extract the bits of data it actually wants to show](https://www.compose.io/articles/using-graphql-with-mongodb/). If some of the data needed by the UI isn't provided by a given resource endpoint, then the client needs to go off to the server and request more data from another URL. Over time, the link between front-end applications and back-end servers can become very rigid. As data gets more complex in structure, it gets harder and slower to query with the traditional REST API. |
There was a problem hiding this comment.
@igorlima I would suggest removing this paragraph from this article. This article is a tutorial/introduction for implementing a GraphQL server, not an opinion piece. The assertions made here in regards to comparisons between ReSTful communication architecture vs GraphQL, don't really fit into the topic or theme of the article. Furthermore, some of the assertions made here aren't necessarily true and could open up the Fanatics Engineering team to a lot of scrutiny.
|
@RavenHursT @igorlima Do y'all wanna merge this still? Trying to get this blog up and running with regular content. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An introduction for GraphQL