Introduction to GraphQL - PHP UK 2018

GraphQL is rapidly becoming a high-profile alternative to RESTful APIs. This talk will go into its advantages, disadvantages, and when it’s appropriate to use as well as how we can interact with it, both as an API consumer, and API producer.

Transcript

1. INTRODUCTION TO GRAPHQL PHP UK CONFERENCE 2018 @MICHAELCULLUMUK
2. INTRODUCTION TO GRAPHQL PHP UK CONFERENCE 2018 @MICHAELCULLUMUK
3. @MICHAELCULLUMUK ME?
4. MICHAEL CULLUM @MICHAELCULLUMUK
5. @MICHAELCULLUMUK GRAPHS
6. @MICHAELCULLUMUK GRAPHS
7. @MICHAELCULLUMUK GRAPHS USER ORGANISATION REPOSITORY ORGANISATION REPOSITORY COMMIT COMMIT COMMIT USER USER USER COMMIT COMMIT COMMIT USER USER USER USER USER USER
8. @MICHAELCULLUMUK REST
9. @MICHAELCULLUMUK REST API GET /repos/:id
 GET /orgs/
 GET /orgs/:id/
 GET /orgs/:id/repos/
 GET /orgs/:id/repos/:id/
 POST /orgs/ 200 OK
 200 OK
 200 OK
 200 OK
 200 OK
 201 Created
10. @MICHAELCULLUMUK REST API { "_links": { "self": “http://api.github.com/orgs/20/repos“ }, "limit": 100, "results": [ { "_expandable": { "commits": “/repos/105/commits“, "collaborators": "/repos/105/collaborators", }, "id": "3965071", "title": “symfony/symfony", "org": “Symfony", ... }, { ... } ], "size": 2, "start": 0 }
11. @MICHAELCULLUMUK GRAPH QL
12. @MICHAELCULLUMUK GRAPHQL IS (1) A QUERY LANGUAGE FOR YOUR API
13. @MICHAELCULLUMUK GRAPHQL IS (2) A SERVER-SIDE RUNTIME FOR EXECUTING QUERIES USING A TYPE SYSTEM YOU DEFINE
14. @MICHAELCULLUMUK WAT?
15. @MICHAELCULLUMUK QUERYING
16. @MICHAELCULLUMUK { me { name } } { "data": { "me": { "name": "Michael Cullum" } } } Request (Graph QL) Response (JSON) BASIC PARAMETER FETCHING
17. @MICHAELCULLUMUK { me { name company } } { "data": { "me": { "name": "Michael Cullum", "company": "SamKnows" } } } Request (Graph QL) Response (JSON) BASIC PARAMETER FETCHING
18. @MICHAELCULLUMUK { me { name repos { name } } } { "data": { "me": { "name": "Michael Cullum", "repos": [ { "name": "michaelcullum.com" }, { "name": "my-cool-library" } ] } } } Request (Graph QL) Response (JSON) BASIC PARAMETER FETCHING
19. @MICHAELCULLUMUK GITHUB
20. @MICHAELCULLUMUK { user(login: "michaelcullum") { name } } Request (Graph QL) Response (JSON) ARGUMENTS { "data": { “user": { "name": "Michael Cullum" } } }
21. @MICHAELCULLUMUK { user(id:"1000") { name height(unit: FOOT) } } ARGUMENTS
22. @MICHAELCULLUMUK GITHUB
23. @MICHAELCULLUMUK THE REQUEST AND RESPONSE MATCH
24. @MICHAELCULLUMUK { me { name company } } { "data": { "me": { "name": "Michael Cullum", "company": "SamKnows" } } } Request (Graph QL) Response (JSON) RECAP
25. @MICHAELCULLUMUK { user { name repos { name } } } { "data": { “user”: { "name": "Michael Cullum", "repos": [ { "name": "michaelcullum.com" }, { "name": "my-cool-library" } ] } } } Request (Graph QL) Response (JSON) RECAP
26. @MICHAELCULLUMUK { fabien: user(login:"fabpot") { name } andrew: user(login:”andrew") { name } } Request (Graph QL) Response (JSON) ALIASES { "data": { "fabien": { "name": "Fabien Potencier" }, “andrew": { "name": "Andrew Nesbitt" } } }
27. @MICHAELCULLUMUK { fabien: user(login: "fabpot") { name email company } michael: user(login: "michaelcullum") { name email company } } Without Fragments With Fragments FRAGMENTS { fabien: user(login: "fabpot") { ...userdetails } michael: user(login: "michaelcullum") { ...userdetails } } fragment userdetails on User { name email company }
28. @MICHAELCULLUMUK GITHUB
29. @MICHAELCULLUMUK OPERATIONS
30. @MICHAELCULLUMUK QUERY OPERATIONS query getUserAndCompany ($login: String!) { user(login: $login) { name company isHireable } } {"login": "michaelcullum"} Request (Graph QL) Variables
31. @MICHAELCULLUMUK QUERY OPERATIONS query getUserAndCompany ($login: String!) { user(login: $login) { name company isHireable @include(if: $hireable) } } { "login": "michaelcullum", “hireable”: true } Request (Graph QL) Variables
32. @MICHAELCULLUMUK GITHUB
33. @MICHAELCULLUMUK MUTATIONS
34. @MICHAELCULLUMUK MUTATION VS QUERYING mutation CreateRepoForUser($user: User!, $repo: RepoInput!) { createRepo(user: $user, repo: $repo) { name Repo } } { "user": "michaelcullum", "repo": { "name": “mailing-lib”, "description": “A library for emails” } }
35. @MICHAELCULLUMUK DEFINE AN INPUT SCHEMA TYPE input RepoInput { name: String! description: String! }
36. @MICHAELCULLUMUK SCHEMAS
37. @MICHAELCULLUMUK OBJECT TYPES type ConferenceTalk { title: String!
 speaker: String! track: Track! ratings: [Review!] }
38. @MICHAELCULLUMUK QUERY TYPE type Query { talk(id: ID!): ConferenceTalk review(id: ID!): Review speaker(name: String!): Speaker }
39. @MICHAELCULLUMUK ▸ String ▸ Int ▸ Float ▸ Boolean ▸ ID SCALAR TYPES
40. @MICHAELCULLUMUK ENUMS enum Track { REDSHIFT MERCARI BYTEMARK }
41. @MICHAELCULLUMUK INTROSPECTION
42. @MICHAELCULLUMUK GITHUB
43. @MICHAELCULLUMUK SERVER-SIDE
44. @MICHAELCULLUMUK COMPOSER REQUIRE WEBONYX/GRAPHQL-PHP
45. @MICHAELCULLUMUK SINGLE ENDPOINT FILE
46. @MICHAELCULLUMUK TYPES $userType = new ObjectType( [ 'name' => 'User', 'description' => 'Our blog visitor', 'fields' => [ 'firstName' => [ 'type' => Type::string(), 'description' => 'User first name', ], 'email' => Type::string(), ], 'resolve' => function() { return [ 'id' => 1, 'title' => 'Example blog post', 'authorId' => 1 ]; } ] );
47. @MICHAELCULLUMUK DEFAULT FIELD RESOLVER
48. @MICHAELCULLUMUK API PLATFORM
49. @MICHAELCULLUMUK REST VS GRAPH QL
50. @MICHAELCULLUMUK ‣ REST AND GRAPHQL ARE TOTALLY DIFFERENT ‣ GRAPHQL ISN'T A MAGIC BULLET, NOR IS IT “BETTER" ‣ YOU CAN DEFINITELY USE BOTH AT THE SAME TIME ‣ GRAPHQL IS DOPE IF USED FOR THE RIGHT THING Phil Sturgeon
51. @MICHAELCULLUMUK REST
52. @MICHAELCULLUMUK GRAPH QL
53. @MICHAELCULLUMUK VERSIONING
54. @MICHAELCULLUMUK ISSUES
55. @MICHAELCULLUMUK CACHING
56. @MICHAELCULLUMUK INFORMATION HIDING
57. THANKS @MICHAELCULLUMUK
58. INTRODUCTION TO GRAPHQL PHP UK CONFERENCE 2018 @MICHAELCULLUMUK