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.
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.