Summary
In this chapter, you were introduced to GraphQL and how to look at it holistically. You learned how the graph is created and what comprises the GraphQL server from a provider viewpoint.
You learned about queries, resolvers, and mutations, as well as how each type field can have an impact on costs and performance.
Developing a GraphQL API follows similar practices to other REST APIs but there were a few wrinkles in how you look at developing a Product plan due to cost factors. You learned that those cost factors provide you with details on how to set up the rating limits in your plan. Adjusting weights at the type level or field level will help determine the cost of your GraphQL API. You also learned how to remove fields from the schema to remove information that you do not wish your consumers to access.
GraphQL is not for every implementation and it certainly doesn't replace your REST APIs, but it does provide benefits in situations where the client needs to determine...