Practical GraphQL: Schema Design and Dev Tools
Details
For our 3rd GraphQL SF meetup, we'll be hearing about GraphQL best practices, from tips on schema design and API generation to developing with browser dev tools.
Event Details
Held at Meteor Development Group's headquarters in San Francisco's SOMA district. Doors open at 6PM. Dinner will be served upstairs, and we'll have drinks on hand as well.
Livestream
If you can't make it in person, we'll be livestreaming this event on Youtube (https://www.youtube.com/watch?v=Wclzls-whKs).
Agenda
6:00pm - Doors open, drinks and dinner served
7:00pm - GraphQL Schema Design: Tips and tricks from the battlefield - Gustav Rydstedt (https://twitter.com/swedishgoose) (CTO & Cofounder, Verbling)
Verbling, as many other companies, started seeing the breaking points of having hundreds of endpoints in a traditional REST interface: backend aggregators, custom caching, and sacrifices in how our front end was structured. A year ago we switched to GraphQL with Relay and today most of our data layer is through GraphQL. This talk is a concrete set of tips and tricks we've learned designing our schema and queries, including unlearning flat queries from REST, individually authenticated fields, contextual edges, and more!
7:35pm - Generating GraphQL APIs for Content-Based Sites - Chris Biscardi (https://twitter.com/chrisbiscardi?lang=en) (Senior Engineer, Dropbox)
When building content-based sites, the content can come from CMS's, git repos, and plain directories of files. How can we structure a system that can compose a GraphQL Schema on top of these disparate sources and enable discovery through tools like GraphiQL?
8:05 pm - Break
8:10 pm - GraphQL Devtools: Easier Developing for Happier Product Devs - Danielle Man (https://twitter.com/danimman) (Software Engineer, Apollo)
People often choose to develop with GraphQL improved performance and easier maintenance. One of its most important benefits is that you can simplify front-end development by avoiding repetition of logic across multiple clients.
Many GraphQL developers use a sophisticated client to handle caching, pagination, and other important (but complex) logic you’d rather not have in your app code. These clients make development much easier and enable richer user experiences, but can also make it harder to understand your app's state management. We wanted to have the best of both worlds, and over time came up with Apollo Client Devtools (https://github.com/apollostack/apollo-client-devtools) for Chrome to give developers a clearer understanding of their data while still taking advantage of the complex functionality inside a caching GraphQL client.
In this talk, I’ll discuss how we made Apollo Client Dev Tools , how they’ve benefitted our workflow so far, and how we think GraphQL lends itself to awesome dev tools in general.
How to get to MDG
Driving? Here's (https://www.parkinsf.com/sanfrancisco/parking-near/140+10th+St/thu/starting-6-00pm/for-3-hours) a helpful guide to parking around our office.
Cycling? You can lock your bike to the parking meters outside of our office.
Taking transit? We're within walking distance of the Civic Center BART/MUNI station.
Walking? See you there!
Practical GraphQL: Schema Design and Dev Tools