August 2020 Summaries

Here's a neutral and interesting summary of the text in one paragraph: The author discusses the importance of avoiding failures, such as introducing breaking changes to a GraphQL schema, by using a feature called client awareness in Apollo Studio. This feature enables understanding which clients are using which fields of the graph, allowing for better maintenance of the schema and reducing engineering time spent on resolving issues. By implementing client awareness, teams can identify usage patterns, clean up old fields, discover use cases, and manage access to their graph with more confidence, ultimately leading to a more efficient development process.

The text discusses building a portable Apollo Server config, which allows developers to run Apollo Server in different environments (Express and AWS Lambda) without duplicating code. The author introduces the concept of a "config object" that can be shared across integrations, encapsulating schema-related code, resolvers, datasources, and context-related logic. The config object is created using a function called `createConfig`, which takes an environment-specific object as input and returns a new config object with the necessary values. This approach enables developers to use the same codebase for local development and production deployment, making it easier to maintain and update their application. The author also discusses how to handle integration-specific code and context-related logic in a way that makes them portable across environments.

The GraphQL Summit Worldwide was held online, attracting over 6000 developers from around the world. The conference featured panels and talks on various topics, including Federation adoption, which is steadily rising as companies look to simplify serving a GraphQL API at scale. Engineers from large enterprise companies such as GitHub, Netflix, American Airlines, StockX, Priceline, and PayPal shared their experiences with Federation. Project Constellation aims to make Federation faster, stronger, and more flexible by introducing a compile step for Federated graphs. The conference also featured a new GraphQL Community Discord channel where attendees could connect with each other and participate in topic rooms on various topics such as Rust, caching, Android, iOS, and livestreaming. The talks were jam-packed with actionable advice from experienced developers, including lessons learned from Gusto, Twitter, and 1stdibs. The conference concluded that this was the best Summit yet, despite the changes, and provided resources for attendees to continue learning and improving their GraphQL skills.