# What I Learned At GraphQL Summit

DevFeed: [What I Learned At GraphQL Summit](<https://devfeed.tech/articles/what-i-learned-at-graphql-summit-23573.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/what-i-learned-at-graphql-summit-f61d6fc6680a>)

Author: Khalil Stemmler

Published: 2019-11-14T18:39:44Z

Content type: article

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [apollo-client](<https://devfeed.tech/topics/apollo-client.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [React](<https://devfeed.tech/topics/react.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>)

Tags: [adopting](<https://devfeed.tech/tags/adopting.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [airbnb](<https://devfeed.tech/tags/airbnb.md>), [api](<https://devfeed.tech/tags/api.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [apollo-client](<https://devfeed.tech/tags/apollo-client.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [beta](<https://devfeed.tech/tags/beta.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [caching](<https://devfeed.tech/tags/caching.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [change](<https://devfeed.tech/tags/change.md>), [change-validation](<https://devfeed.tech/tags/change-validation.md>), [changes](<https://devfeed.tech/tags/changes.md>), [client](<https://devfeed.tech/tags/client.md>), [code](<https://devfeed.tech/tags/code.md>), [community](<https://devfeed.tech/tags/community.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [san-francisco](<https://devfeed.tech/tags/san-francisco.md>), [summit](<https://devfeed.tech/tags/summit.md>), [toronto](<https://devfeed.tech/tags/toronto.md>)

## AI overview

GraphQL Summit attendees described GraphQL as a mature, growing approach for increasingly complex client-side experiences. The excerpt highlights simpler client data fetching and improved developer experience and velocity. It recommends incremental adoption: GraphQL can coexist with REST while teams convert operations gradually; Apollo Client's React Hooks are also praised as pleasant to use. Large deployments still face service-architecture challenges. The excerpt names federation as a way to let cross-cutting teams develop separate graphs and avoid error-prone monoliths, and schema change validation as protection against breaking live production queries. Caching is mentioned across client, server, and intermediary layers, but the excerpt cuts off before further details.

## Source excerpt

This year, I flew out to San Francisco to attend (and help host!) my very first GraphQL Summit. As a Canadian flying to San Francisco for the first time, I was delighted to escape the Toronto cold to explore a new city, meet my awesome new Apollo colleagues, hang out with puppies (oh yeah--we had a puppy booth 🐶), chat with devs from around the world, and of course learn everything I could about the present and future of GraphQL.