Graphql

  • the client determines what data they want, how they want it, and in what format they want it in.

Advantages

  • it typically delivers the smallest possible request.

  • Avoids issues that REST have, where the client might need to make multiple requests

  • Standardised language to do the communication, like sql style

Disadvantages

  • As this turns multiple request into one request, the complexity is moved to the database (or cache), which can overload the db

Uses

  • GraphQL can be more useful in specific use cases where a needed data type is well-defined, and a low data package is preferred.

Links

  • https://medium.freecodecamp.org/graphql-java-development-stack-in-production-21f402c4c37a

  • https://www.howtographql.com/graphql-java/0-introduction/

  • https://www.baeldung.com/spring-graphql

  • https://github.com/graphql-java/graphql-java-http-example

  • https://self-learning-java-tutorial.blogspot.com/2019/10/spring-boot-graphql-tutorial.html

  • https://www.freecodecamp.org/news/a-beginners-guide-to-graphql-60e43b0a41f5/

  • https://www.freecodecamp.org/news/graphql-java-development-stack-in-production-21f402c4c37a/

PreviousegressNextIdempotency

Last updated