How Netflix API evolved through 4 stages

From Netflix TechBlog (2020) & a LinkedIn post -

Netflix is known for its loosely coupled and highly scalable microservice architecture. Rather than exposing 100s of microservices to UI developers, Netflix offers a unified API aggregation layer at the edge. Netflix's Studio Ecosystem architecture has evolved in distinct phases, all motivated by reducing the time between idea and implementation, improving the developer experience, and streamlining operations. The architectural phases look like:

𝟭. 𝗠𝗼𝗻𝗼𝗹𝗶𝘁𝗵

Like everyone else, Netflix started with a monolithic architecture where the entire application was packaged and deployed as a single entity.

𝟮. 𝗗𝗶𝗿𝗲𝗰𝘁 𝗔𝗰𝗰𝗲𝘀𝘀

To improve team autonomy and speed, the monolith was split into microservices. Each client made direct requests to the microservices. But with hundreds of them, exposing everything wasn't ideal.

𝟯. 𝗚𝗮𝘁𝗲𝘄𝗮𝘆 𝗔𝗴𝗴𝗿𝗲𝗴𝗮𝘁𝗶𝗼𝗻 𝗟𝗮𝘆𝗲𝗿

They built an API Gateway to bind all the services together and presented a unified front to the clients.

The API Gateway was supposed to bring order, but instead it became the new monolith as team grew and services multiplied.

𝟰. 𝗙𝗲𝗱𝗲𝗿𝗮𝘁𝗲𝗱 𝗚𝗮𝘁𝗲𝘄𝗮𝘆

They built a federated GraphQL gateway to dismantle the API gateway monolith. The federated gateway eliminated complicated business logic, now routing queries directly to responsible services and stitching responses together.