Let's talk about GraphQL
0 likes216 views
The document introduces GraphQL as a query language and server-side runtime for APIs, emphasizing its advantages over RESTful APIs, such as a single endpoint that eliminates overfetching and underfetching. It highlights the popularity of GraphQL and includes references to a visualization of a Game of Thrones graph dataset. Additionally, it notes that while GraphQL is gaining traction, it remains relatively new with limited libraries available.
Let's talk about GraphQL
- 2. Renato Selenica ● A Lazy Developer ● All Things JavaScript ● Angular/React/Node @renatoselenica
- 3. Table of Contents ● GraphQL intro ● Differences from RESTful ● Some CODEEE
- 4. -https://graphql.org/learn/ GraphQL is a query language for your API, and a server-side runtime for executing queries by using a type system you define for your data.
- 5. GraphQL is a specification. A set of rules to define how data travels from the client to the server.
- 6. -Kensho blog A visualization of a subset of the Game of Thrones graph dataset with compiled GraphQL. Blue vertices correspond to characters, red vertices are noble houses, and orange vertices represent regions in the Game of Thrones world. Adapted from the Creative Commons dataset available at https://orientdb.com/public- databases/GamesOfThrones.zip
- 7. It’s getting really popular
- 10. But why?
- 12. Call a single endpoint
- 14. Strongly Typed
- 15. On the other side...
- 16. GraphQL is still new
- 17. A few libraries in the scene
- 18. Power to the client
- 19. Prisma
- 21. Demo Time