React + Relay + GraphQL is the Future

2. @keithpitt
5. I’m excited! ⚡
6. But first…history
7. + Probably the Future +
8. Glad I said “probably”
9. + Probably the Future +
10. + Probably the Future +
11. + + Is the future.
12. React
15. Just the UI Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
17. + Backbone
18. + Flux
19. +
27. Too many random “Restful” JSON endpoints
28. The server and the client were coupled
29. Inefficient and slow
30. Too much code
31. Lots of boiler plate
32. Hard to get started
33. Telstra
36. GraphQL
37. Relay
38. GraphQL
41. CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/ projects/buildkite/23
43. CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/ projects/buildkite/23?expand=comments
44. CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/ projects/buildkite/23/comments
48. A specification
49. It’s represents data how we think about it
50. It looks like JSON
51. Simple HTTP Post
52. You control what data is returned
53. Typed
54. Introspection
57. IDE integration
58. Before commit hook validation
62. Relay
63. The glue between GraphQL and React
67. Demo
68. Relay
69. Batched requests
70. Partial data fetching
71. Telstra
72. Things I skipped:
73. Things I skipped: Webpack + Rails Mutations Security + Authorisation Routes Subscriptions ES6,7,8,9,10,xx Probably more…
74. Get excited ⚡
75. + + Is the future.
78. Demo
86. CURL -X POST \ -H "Authorization: Bearer xxx" \ https://graphql.buildkite.com/v1 \ -d '{ "query": "query AwesomeQuery { viewer { user { name } } }" }'
87. Fin ❤ @keithpitt