Download as PDF, PPTX
Uploaded byiMasters
InterCon 2017 - Tudo o que você quer saber sobre GraphQL - Ubiratan Soares
This document discusses GraphQL and how it compares to REST APIs. It outlines some common issues with REST APIs like versioning headaches and making multiple requests to fetch needed data. The core concepts of GraphQL are then explained, including how it uses a single endpoint and schema to define the data contract. Queries and mutations are covered as the main operations in GraphQL along with its type system. Potential concerns about using GraphQL for businesses are addressed at the end.
More Related Content
Similar to InterCon 2017 - Tudo o que você quer saber sobre GraphQL - Ubiratan Soares
InterCon 2017 - Tudo o que você quer saber sobre GraphQL - Ubiratan Soares
- 1. EVERYTHING YOU WANT KNOWABOUT GRAPHQL Ubiratan Soares October / 2017
- 2.
- 3.
- 4.
- 5.
- 7.
- 8.
- 9. REST WAS NOTDESIGNED WITH NOWADAYS APPLICATIONS, DEVICES AND USERS IN MIND …
- 10.
- 12.
- 13.
- 14. GET https://api.xyz/v1/products/123456789?arg1=value1&arg2=value2 GET https://api.xyz/v2/products/123456789?arg1=value1&arg2=value2 GEThttps://api.xyz/v3/products/123456789?arg1=value1&arg2=value2 GET https://api-v1.xyz/products/123456789?arg1=value1&arg2=value2 GET https://api-v2.xyz/products/123456789?arg1=value1&arg2=value2 GET https://api.xyz/products/123456789?arg1=value1&arg2=value2&version=1 GET https://api.xyz/products/123456789?arg1=value1&arg2=value2&version=2 GET https://api.xyz/products/123456789?arg1=value1&arg2=value2 Accept: application/api.version.v1 + json Accept: application/api.version.v2 + json
- 15.
- 17. MULTIPLE ENDPOINTS TO SOLVEA SPECIFIC NEED FROM CLIENT
- 18. ENDPOINT EXPOSES MORE DATATHAN CLIENT NEEDS PER HTTP REQUEST
- 20.
- 21.
- 22. Well defined contract Clientand server must respect a schema for effective data exchange 2
- 23. No more overfetching GraphQLclients can fetch only the data they really need for a given purpose 3
- 24. 4 No more underfetching GraphQLclients can retrieve all the data they need into a single HTTP call : no more chained and/or parallel HTTP requests
- 26.
- 28. Field name !=Type name
- 29. QUERY (IP) LOCDATA city :city location : location LOCATION latitude : String longitude : String time_zone : String CITY geoname_id : String names : cityNames ACCEPTS RETURNS . . . . . . CITYNAMES de : String en : String ru : String . . .
- 30.
- 31. { getLocation(ip: “172.59.226.170") { country{ names { en } geoname_id iso_code } location { latitude longitude } } } Operation Root Query parameter Data that actually matters
- 32. { getLocation(ip: “172.59.226.170") { country{ names { en } geoname_id iso_code } location { latitude longitude } } } "For the available data, return the English name for the country"
- 33. { getLocation(ip: “172.59.226.170") { country{ names { en } geoname_id iso_code } location { latitude longitude } } } "For the available data, return the latitude and the longitude from the geolocation info"
- 34. { "data": { "getLocation": { "country":{ "names": { "en": "Brazil" }, "geoname_id": "3469034", "iso_code": "BR" }, "location": { "latitude": "-23.5733", "longitude": "-46.6417" } } } } QUERY
- 36. MORE ABOUT OPERATIONS •Data payload will mirror the type hierarchy defined on schema • All data types for queries/mutations must be defined on schema • Operation can accept parameters and/or variables • We can form better, readable blocks for operations using aliases and fragments • Etc
- 37. CLIENT INTENT REST+ HTTP GraphQL + HTTP GraphQL Operation READ RESOURCE GET POST QUERY CREATE RESOURCE POST POST MUTATION UPDATE RESOURCE PUT POST MUTATION REMOVE RESOURCE DELETE POST MUTATION
- 38.
- 48.
- 49. REMEMBER, FOLKS • GraphQLis just a spec • GraphQL aims to solve some of well know issues from REST • There are lots of great options for clients and servers for GraphQL APIs • GraphQL is mobile friendly, but it brings its own set of challenges • GraphQL no longer uses the Triple-BSD + Patents licensing model
- 50. UBIRATAN SOARES Computer Scientist byICMC/USP Software Engineer, curious guy Google Developer Expert for Android Teacher, speaker, etc, etc
- 51.