You are viewing content from a past/completed QCon Plus - November 2020

Session

How Netflix Scales its API with GraphQL Federation

Netflix is known for its loosely coupled and highly scalable microservice architecture. Rather than expose 100s of microservices to UI developers, Netflix offers a unified API aggregation layer at the edge. But as our business has scaled globally, our ability to innovate rapidly is approaching an asymptote due to the growing number of developers and increasing complexity of the domain. How do you scale out a microservice architecture while providing a single, unified API that enables rapid UI innovation decoupled from a swaying sea of microservices?

In order to address this growing problem, we’ve developed a federated GraphQL platform to power the API layer. This solves many of the consistency and development velocity challenges with minimal tradeoffs on dimensions like scalability and operability. In this talk, we’ll share the story of developing the federated API layer for Netflix’s studio ecosystem and explore possibilities and concerns for applying this approach to other domain areas.

Main Takeaways

1 Find out how Netflix takes API aggregation to the next level with Federated GraphQL.

2 Learn that you can implement a company-wide unified API without building a monolith.


Jennifer. Stephen, what is your work these days?

Stephen: These days, I've been changing lots of diapers and making blueberry-banana pancakes with my two-year-old (I'm on parental leave right now.) Prior to that I spent the last year building a platform for APIs that allows teams at Netflix to iterate more quickly by exposing their APIs directly to the UIs and to the consumer. It's this Federated GraphQL platform that we’ll be talking about.

Jennifer: I work on the Netflix API team. For the past several months, I’ve been working on a multi-team initiative to deliver a Federated GraphQL prototype for the Netflix consumer experience.

What is the goal of your presentation?

Jennifer: For many organizations, API aggregation has historically meant an orchestration tier that's full of logic. We are hoping that after this talk, people could rethink what API aggregation means, that it can simply be a platform that enables APIs to be aggregated, without necessarily housing any business logic in order to achieve this.

What would you like attendees to walk out of the presentation with?

Stephen: Enlightenment and inspiration. Also some API stuff.


Speaker

Jennifer Shin

API engineers for Netflix's consumer and studio experiences

Jennifer Shin is a member of the API Systems team at Netflix where she scales APIs for both the content production and streaming worlds. Delivering highly available content to millions of users worldwide and designing APIs with a view toward availability and usability has been a joy and all-time...

Read more

Speaker

Stephen Spalding

API engineer for Netflix's consumer and studio experiences

Stephen Spalding first encountered the joys of distributed systems while writing multiplayer games for the TI-83 during math class in 8th grade. After earning Master’s degrees in electrical engineering and image processing from GA Tech and ENSEEIHT respectively, Stephen dove into medical...

Read more
Find Stephen Spalding at:

From the same track

Session

How to Tame Your Service APIs: Evolving Airbnb’s Architecture

Wednesday Nov 11 / 12:50PM EST

Airbnb was reaping the benefits of its migration to services, but soon managing hundreds of services and thousands of APIs created new problems. The dependency graph became too complicated, which impacted scalability, reliability, and velocity. Airbnb is tackling these challenges via introducing...

Jessica Tai

Engineering Manager of Homes Platform Infrastructure @Airbnb

Session

Rebuilding Twitter’s public API

Wednesday Nov 11 / 01:40PM EST

In August 2020, Twitter launched v2 of our API on top of a new architecture that could more easily scale with the large number of API endpoints we plan to deliver in the future.  As part of this design process, we drafted goals around Abstraction, Ownership, and Consistency. With the above...

Steve Cosenza

Tech Lead of the DES API Team @Twitter

PANEL DISCUSSION

Panel: Past & Present API Architectures: What, Why, How & When

Wednesday Nov 11 / 02:30PM EST

Choosing an API architecture requires understanding the options and various tradeoffs. Rather than copy another company's architecture, we should seek to understand what led to that architecture and its relative pros/cons. In this panel, we'll explore the multiple API architectures that...

Jennifer Shin

API engineers for Netflix's consumer and studio experiences

Stephen Spalding

API engineer for Netflix's consumer and studio experiences

Steve Cosenza

Tech Lead of the DES API Team @Twitter

View full Schedule

Less than

15

weeks until QCon Plus May 2022

Level-up on the emerging software trends and practices you need to know about.

Deep-dive with world-class software leaders at QCon Plus (Nov 1-12, 2021).

Save your spot for $549 before February 7th

Register