GraphQL over REST.

Without writing new endpoints to build and update the functionality of the application. Just write a GraphQL query, Apollo gets it for you and coordinates the whole stack

Most importantly, Apollo already has a built in technology, so you can add a little time to it. It also applies to the whole GraphQL norm and all community GraphQL tools

GraphQL Facebook just thinks of several types of servers. They can write specifications to the server and the server is written about how to request a type response. REST than GraphQL API, to describe the exact needs of client data, so that no more data has been read in order to borrow or get excessive. --- It is both life and barricades, but we are over. Special cloth police. Please do not play yourself. The key to success is the primary key of speaking the cloth more than once massage a very important week. Some CSS Grid code again, stop Gatsby's development server and turn off your broswer window. // localhost: 8000 / another - 1 Gatsby again develops and runs open HTTP. It will be as follows.

Let's take a look at the GraphQL method. Custom endpoint ideas are included and play it extremely and GraphQL on the server. However, the server's endpoint, channel is not important. Of course if we do this via HTTP, HTTP the way is not important. Suppose we disclose GraphQL to endpoint via HTTP / graphql. Read the expression requirements again in English and compare it with the GraphQL query. It is as close as possible to it. Now, we started with the original JSON data, this GraphQL query. The GraphQL query is an exact structure of JSON data, except that all "value" sections are not. If we consider this question from the viewpoint of the relationship between question and answer, the questionable answer mentioned a part of the answer

Star Wars hosts https://github.com/graphql/swapi-graphql, and has an API for data GraphQL. We continue to try to build people objects into the data there. We will explain some of the nuances, but you can use this API here (official inquiries to read the view of the data requirements to Darth Vader for example). A more important threat of service is a resource exhaustion attack (GraphQL attack making AKA rejection). The GraphQL server may be subject to attacks by overly complex queries, and these queries occupy all resources of the server. Query Deeply Nested Relationship (User -> Friends -> Friends ......) Very simple, or use field alias, repeatedly request the same field. Resource exhaustion attacks are not specific to GraphQL, and we must be careful when using GraphQL