Join us for our first pop up meetup, with talks from Apollo (https://www.apollodata.com/) team members James Baxley (https://twitter.com/jbaxleyiii) and Sashko Stubailo (https://twitter.com/stubailo), as well as Kyle Matthews (https://twitter.com/kylemathews) creator/maintainer of GatsbyJS (https://www.gatsbyjs.org/)!
Joel Griffith - ???
Modular GraphQL - Sashko Stubailo
One of the biggest benefits of GraphQL is that it lets you fetch all of the data you need in one query. It's also super useful to have a complete description of all the data available in one schema. However, this seems to be in direct conflict with a recent trend towards microservices and decoupling, since it implies that you need to have exactly one main GraphQL service that runs your entire schema.
In this talk, we'll look at different ideas for how a GraphQL server could be split into multiple parts. This can help distribute schema ownership across teams, make your versioning and orchestration more flexible, and help reduce the risk of a single point of failure, while keeping all of the efficiency and organization benefits you expect from GraphQL.
Statically Typing your GraphQL App - James Baxley
Using GraphQL in a static site generator (Gatsby) - Kyle Matthews
Gatsby is a blazing-fast static site generator for React. Its recent new major release unveiled a new plugin-driven data layer which automatically creates a GraphQL schema based on your data sources (e.g. markdown files or headless CMS).
Based on this schema, you then write GraphQL queries in your components to pull in data as needed. At build time, the queries are run and results written out as JSON files leaving a completely static site that can deployed to static site hosts. GraphQL lets Gatsby combine the power and flexibility of database driven sites with the speed and simplicity of static sites.