GraphQL was open sourced three years ago, and released within the context of a client/front-end ecosystem: React. GraphQL has strong adoption and momentum within these front-end communities. GraphQL was also released into a world moving quickly towards fine-grained microservices. As a result, most GraphQL server-side implementations are thin integration layers over REST APIs or microservices that require minimal changes to existing backend architectures. This talk will argue that is time to make more of our backend systems “GraphQL-Native” and that this approach can reduce the architectural and conceptual costs of adopting a fine-grained microservices architecture.

In 2016, Shopify began using GraphQL in production. The following year, we launched our first public GraphQL API. Now, we are rapidly scaling our GraphQL APIs both internally and externally changing engineering processes and teams along the way. This is a story about how we scale GraphQL at Shopify.

TBA

GraphQL specifies what data and response shape we need and not how to get and reshape that data. At Twitter, we automatically translate GraphQL queries into code that efficiently specifies the how as well! See how we keep our API uniform and extend it without writing or deploying new code.

This talk presents a formal study of the GraphQL language. After a gentle introduction to the typical problems considered in such studies, I highlight our findings regarding these problems for the case of GraphQL. As a bonus, I present a solution to avoid producing overly large query results.

At Docker, we began using GraphQL in an unconventional way -- without a server. Using a client-side schema we gained major benefits from GraphQL with a smaller buy-in. Today we are moving our GraphQL interface to the server and exploring new technologies like GraphQL bindings, ReasonML, and more.

After 5 years, we're building the next generation infrastructure at Medium with GraphQL and we're doing it without slowing product development and we're incrementally gaining benefits from the new system. See how we take advantage of GraphQL to enable widespread yet gradual architectural change!

How we used SDL, custom directives and a little expression language to unlock the GraphQL flexibility we needed. Bringing the power of GraphQL to XING is an ongoing challenge and we'd like to show you some of our answers to the most pressing question we faced down that road.

GraphQL is designed to be easy to use, but newcomers to GraphQL are often tripped up by common problems and misconceptions. I'll cover how to teach GraphQL in a way that gets newbies excited ands helps them overcome the mental hurdles that prevent them from being productive with GraphQL.

GraphQL is all about enabling frontend developers to build products faster. With Apollo Server 2.0, we've made GraphQL server development more approachable for product developers, thanks to a simpler API that works in every environment.In this talk, you'll not only learn about Apollo Server 2.0's exciting new features, you'll also hear Apollo's vision for the future of GraphQL servers, including a sneak peek of what's beyond 2.0.

At Samsara, we've used live queries in production for the last two years to render live data in our applications by default with minimal boilerplate and plumbing. We'll discuss our experiences: reactive backends, developer happiness, and how you too can add live queries to an existing system.

GitHub has had a REST API for almost 10 years and it's powered hundreds of thousands of integrations. In the last 2 years, GitHub has been reinvesting in its platform and brought a new, public GraphQL API to market. Additionally, GitHub's engineers build, maintain, and use their own GraphQL APIs to power GitHub.com itself. In this talk, Nick will share why GitHub is enabling integrators to build more powerful integrations, why GraphQL is an important part of the strategy, and all the joy, tears, bad code, and amazing accomplishments of our journey.