Speaker
Abstract
GraphQL is steadily gaining popularity as an API technology choice for Client to Server communication. However, it can be daunting to realize the benefits of GraphQL without significant investment. Furthermore, there are migration pains and multiple architectural patterns for a GraphQL API strategy. Is it worth it?
At Netflix, we have been operating a Federated GraphQL platform where developers can contribute to the unified GraphQL API. This platform powers APIs for everything from Netflix Streaming to the Netflix Studio applications and most recently, internal development tools.
In this presentation, I will share
- Key value propositions and some common misconceptions of GraphQL
- Pros and Cons of Monolithic versus Federated GraphQL architecture
- Challenges and lessons from operating the Federated GraphQL platform and some criteria to consider before adopting this approach
- Best Practices for Schema Design and Evolution that will set you and your organization up for success
- Developer tools we have built to facilitate collaborative schema design and ease GraphQL development.
Topics
QCon San Francisco 2022 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
Part of the track
Modern APIs: Building and Evolving Hosted by Thomas Betts Senior Laureate Software Architect @BlackbaudFrom the same track
Tuesday 25 October
10:35 Ballroom BC Session Application Programming Interface API Evolution Without Versioning Brandon Byars North America Head of Technology @thoughtworks Versioning is usually the first–and too often, the only–technique architects reach for when imagining a breaking change to an API’s interface. Based on my experience managing the evolution of a public API, I’ve recently cataloged several alternative techniques and their tradeoffs. 11:50 Pacific DEKJ Session Application Programming Interface What API Product Managers Need Deepa Goyal Product Strategy @Postman, previously Product Developer @PayPal & @Twilio With thousands of APIs being built across the industry, serving millions of developers worldwide, and driving billions in revenue, there is a need to manage APIs as products. Building great API products requires both building technically sound APIs and creating an API experience to match. 13:40 Ballroom BC Session Application Programming Interface Scaling GraphQL Adoption at Netflix Tejas Shikhare Senior Software Engineer @Netflix GraphQL is steadily gaining popularity as an API technology choice for Client to Server communication. However, it can be daunting to realize the benefits of GraphQL without significant investment. 14:55 Ballroom BC Session [Panel] Who Cares About Your API? Brandon Byars, Jim Barton, Deepa Goyal, Tejas Shikhare Who cares about your API? Everyone. DevOps has shown us that when developers care about operations, they write better software. What other viewpoints should developers consider when they're building software? 16:10 Seacliff D Session Unconference: Modern APIs Shane Hastie Global Delivery Lead for SoftEd and Lead Editor for Culture & Methods at InfoQ.com What is an unconference? At QCon SF, we’ll have unconferences in most of our tracks. 17:25 Ballroom BC Session Application Programming Interface Sidecars, eBPF and the Future of Service Mesh Jim Barton Field Engineer @Solo, previously @Redhat @Amazon & @Zappos Controversy over the future of service meshes and their architectures is swirling. This is a vital discussion as enterprise migration to microservice and Kubernetes-based architectures continue. This talk incorporates the latest community developments to explore what the future looks like.