GraphQL

• developed in response to REST, to execute precise syntax that retrieves only what is needed, lightening payload and simplifying process significantly
• start by creating a schema that describes all the possible queries and the specific types that they return.
• PROS
  • API queries are transparent and well documented, giving users all the information they need to use it effectively
  • precise results, detailed error messages, and flexible permissions help round out a well-balanced but high-functioning API
• CONS
  • too many nested fields in any one request can lead to bad performance
  • requires custom efforts to achieve proper caching
  • GraphQL difficult to pick up without lots of training and experience.