3 December 2019
Yay! We are back with another super duper meetup! Are you for real? Yeah doh... *Twitter* will be hosting again with their largest room and delicious catering! If you haven't joined yet this will be a great opportunity to meet and greet the largest GraphQL community in the world. That's right! We have been around since 2016 and today I'm happy to announce GraphQL SF is now part of our family too! Woot!? Yeah... Now, that IS cool! ✨🦄
Talks and Speakers
• Fix your microservice architecture with GraphQL (by Ruben Oostinga)
Ruben is a software development consultant at Xebia. Originally a backend developer. Nowadays he leverages his software engineering skills to avoid having to rebuild the frontend every couple of years.
GraphQL provides a simple way to query data across your microservices. This pattern of API composition gives frontend developers more flexibility to create the best user experience. However, when applying it to a real world microservice architecture you need to think about preserving team autonomy, migrating existing services, caching and security.
This talk will explain why GraphQL will solve many technical and organisational challenges so you can focus on building business value. I will discuss topics like federation, managed GraphQL services, persistent queries, swagger-to-graphql and the n+1 problem.
• Scaling GraphQL Beyond a Backend For Frontend (by Michelle Garrett)
Michelle is a Software Engineer at Condé Nast in London, where she builds the Vogue and GQ websites.
How do you scale your GraphQL API beyond a single consumer? This talk will discuss the Backend For Frontend pattern, and transitioning a client-specific GraphQL layer into a published API for multiple consumers.
• GraphQL ResolveInfo Deep Dive (by William Lyon)
William Lyon is a software engineer at Neo4j, the open-source graph database, where he works on building integrations and helping developers build applications with graphs.
In this talk I want to explore the content of the resolve info object and how it can be used for generating efficient database queries inside resolvers. We will show how the query AST and GraphQL schema representation in the resolve info object allow us to generate a single database query to resolve any arbitrary GraphQL request.