This is a continuation

In this hands-on tutorial, we’ll build a federated GraphQL API inspired by Netflix’s architecture. We’ll start with three microservices: Users, Movies, and Review and unify them under Apollo Router. By the end, you’ll see how a single query can fetch data across services, just like Netflix handles billions of requests. Whether you're new to Federation or looking to scale, this is your step-by-step guide.

Resources:
- ByteMonk Blog: https://blog.bytemonk.io/
- System Design Course: https://academy.bytemonk.io/courses
- LinkedIn: https://www.linkedin.com/in/bytemonk/
- Github: https://github.com/bytemonk-academy (Code will be pushed soon)
- Previous GraphQL Video: https://youtu.be/i_-q6dT7l1U?si=YPjWU4fNC4u-P6zk

Timestamps
0:00  Netflix’s GraphQL Secret 
0:12  Recap: Netflix’s GraphQL Federation Architecture
0:30  What We’re Building Today (3 Services + 1 Router)
1:10  Architecture Overview: Users, Movies, Reviews
2:05  Federation vs Schema Stitching
3:05  Core Federation Concepts Explained
4:10  Project Structure (Monorepo + Team Ownership)
5:05  Users Subgraph: Identity with @key
6:15  Entity Resolution and __resolveReference
7:05  Movies Subgraph: Same Pattern, Different Owner
7:45  Reviews Subgraph: Entity Extension
8:50  Returning Entity References (Decoupled Services)
9:30  Apollo Router: Composing the Supergraph
10:09 monday.com 
11:26 The Apollo Router, What You Actually Built + Next Steps

https://www.youtube.com/playlist?list=PLJq-63ZRPdBt423WbyAD1YZO0Ljo1pzvY
https://www.youtube.com/playlist?list=PLJq-63ZRPdBssWTtcUlbngD_O5HaxXu6k
https://www.youtube.com/playlist?list=PLJq-63ZRPdBu38EjXRXzyPat3sYMHbIWU
https://www.youtube.com/playlist?list=PLJq-63ZRPdBuo5zjv9bPNLIks4tfd0Pui
https://www.youtube.com/playlist?list=PLJq-63ZRPdBsPWE24vdpmgeRFMRQyjvvj
https://www.youtube.com/playlist?list=PLJq-63ZRPdBslxJd-ZT12BNBDqGZgFo58

#graphql #rest #bytemonk #distributedsystems

GraphQL Federation: The Architecture That Powers Netflix's 70+ Microservices