Why Netflix built an evolutionary architecture

As Netflix continues its journey beyond 100M members, the company is rearchitecting its critical Playback API service to better serve its business needs for the next three to five years. Suudhan Rangarajan discusses why and how Netflix rebuilt the Playback API service and outlines a rigorous framework that you can use to reason about your microservice architecture.

As Netflix continues it journey beyond 100M members, the company is rearchitecting its critical Playback API service to better serve its business needs for the next three to five years. Suudhan Rangarajan discusses why and how Netflix rebuilt the Playback API service and outlines a rigorous framework that you can use to reason about your microservice architecture. The Playback API service is responsible for orchestrating workflows whenever a user watches a title on Netflix. In its seven-year journey, the service has gone through three major rearchitectures: it began as a traditional monolith, where the API and its associated business functions were all part of the same service. For take two, the company cracked the monolith open into a few key microservices, but, in the process, it inadvertently built a distributed monolith with tight coupling and thick client libraries. With this third version, the goal is to break away from a distributed monolith and build an evolutionary microservice architecture which places change-driven design above all other principles. Suudhan offers a deep dive into how Netflix used a goals-based approach to iteratively develop the architecture. Along with providing necessary motivation behind the company’s goals, he explores the choices it considered and how it arrived at an evolutionary architecture. If you’re thinking about rearchitecting any of your systems or planning to build a new set of services, this is the talk for you.