You are viewing content from a past/completed conference.
Scaling GraphQL Adoption at 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. 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.
Speaker
Tejas Shikhare
Senior Software Engineer @Netflix
Tejas is a Senior Software Engineer at Netflix where he works on the API Systems team. He has spent the last 4 year building Netflix's Federated GraphQL platform and helped to migrate Netflix’s consumer facing APIs to GraphQL. Aside from GraphQL, he also enjoys working with distributed systems and has a passion for building developer tools and education.
Find Tejas Shikhare at:
From the same track
Session
Application Programming Interface
API Evolution Without Versioning
Tuesday Oct 25 / 10:35AM PDT
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.
Brandon Byars
North America Head of Technology @thoughtworks
Session
Application Programming Interface
What API Product Managers Need
Tuesday Oct 25 / 11:50AM PDT
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.
Deepa Goyal
Product Strategy @Postman, previously Product Developer @PayPal & @Twilio
Session
Application Programming Interface
Sidecars, eBPF and the Future of Service Mesh
Tuesday Oct 25 / 05:25PM PDT
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.
Jim Barton
Field Engineer @Solo, previously @Redhat @Amazon & @Zappos
Session
[Panel] Who Cares About Your API?
Tuesday Oct 25 / 02:55PM PDT
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?
Brandon Byars
North America Head of Technology @thoughtworks
Jim Barton
Field Engineer @Solo, previously @Redhat @Amazon & @Zappos
Deepa Goyal
Product Strategy @Postman, previously Product Developer @PayPal & @Twilio
Tejas Shikhare
Senior Software Engineer @Netflix
Session
Unconference: Modern APIs
Tuesday Oct 25 / 04:10PM PDT
What is an unconference?
At QCon SF, we’ll have unconferences in most of our tracks.
Shane Hastie
Global Delivery Lead for SoftEd and Lead Editor for Culture & Methods at InfoQ.com
