You are viewing content from a past/completed QCon
Interactive Session

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

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 Netflix & Twitter have built, diving into what led to each and where each might be appropriate to use in other settings.


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 high point in her career. Prior to joining Netflix, she worked on APIs for the New York Times, witnessing first hand the critical role of technology in the spread of information. In her free time, Jennifer enjoys reading and talking about theories of consciousness, the future of AI, simulation theory, and her dog Cloud.


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 imaging algorithms for GE Healthcare before pivoting to nuclear control systems for the Tennessee Valley Authority and then messaging systems for OpenTable. Stephen now distributes systems at Netflix as a Senior Software Engineer.

Find Stephen Spalding at:


Steve Cosenza

Tech Lead of the DES API Team @Twitter

Steve Cosenza is a Senior Staff Software Engineer at Twitter where for the last 8 years he's built HTTP and stateful streaming systems as well as the underlying open source Finatra framework that powers them. Steve has a BS in Computer Science from Cornell University, and a MS in Information Systems from Johns Hopkins Carey Business School. He currently lives in San Francisco, CA with his wife Sara and their fluffy puppy Charlotte.

Find Steve Cosenza at:

From the same track

View full Schedule

3 weeks of live software engineering content designed around your schedule.

Don’t miss out! Save your seat now