Transforming the Monolith into a Federated Graph
summary
TV2 Danmark migrates a single GraphQL gateway serving video metadata into a federated graph after deciding to rewrite the video platform two and a half years ago, handling 900,000 subscribers and about 3 billion ops/month with a 100 ms latency target. A third‑party metadata service becomes a scaling bottleneck so the team changes ID space, rewrites services cautiously, uses the Strangler pattern where possible, and groups playback logic so a playback gateway exposes the schema while downstream components remain REST to avoid extra round trips and preserve performance.
AI-written summary · about
chapters (5)
related talks
06mEscape the GraphQL Monolith
46mMoving to GraphQL
59mBuilding Distributed GraphQL APIs
30mDeep Learnings Migrating legacy services to Federated GraphQL
07mshare how avoid these GraphQL pitfalls
36mConverging Paramount EPG Architectures with GraphQL
50mDistributed GraphQL APIs: Breaking Down Monoliths & Unlocking Agility for Dev Teams
37mGraphQL and Microservices or How we learned to be big and small at the same time