View Slide
@keithpitt
I’m excited! ⚡
But first…history
+Probably the Future+
Glad I said “probably”
+ +Is the future.
React
Just the UILots of people use React as the V in MVC.Since React makes no assumptions about therest of your technology stack, it's easy to try itout on a small feature in an existing project.
+Backbone
+Flux
+
Too many random“Restful” JSONendpoints
The server and the clientwere coupled
Inefficient and slow
Too much code
Lots of boiler plate
Hard to get started
Telstra
GraphQL
Relay
CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/projects/buildkite/23
CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/projects/buildkite/23?expand=comments
CURL -X POST https://api.buildkite.com/v1/organizations/buildkite/projects/buildkite/23/comments
A specification
It’s represents data how wethink about it
It looks like JSON
Simple HTTP Post
You control what data isreturned
Typed
Introspection
IDE integration
Before commit hookvalidation
The glue between GraphQLand React
Demo
Batched requests
Partial data fetching
Things I skipped:
Things I skipped:Webpack + RailsMutationsSecurity + AuthorisationRoutesSubscriptionsES6,7,8,9,10,xxProbably more…
Get excited ⚡
CURL -X POST \-H "Authorization: Bearer xxx" \https://graphql.buildkite.com/v1 \-d '{ "query": "query AwesomeQuery { viewer { user { name } } }" }'
Fin ❤@keithpitt