GraphQL Federation with Apollo and NestJS | SQL to GraphQL | GraphQL Complete Course

Video Description

This video explains End to End Demo to implement Graphql Federation with 3 different GraphQL servers and a Federation gateway To get the most out of GraphQL, your organization should expose a single data graph that provides a unified interface for querying any combination of your backing data sources. However, it can be challenging to represent an enterprise-scale data graph with a single, monolithic GraphQL server. To remedy this, you can divide your graph's implementation across multiple composable services with Apollo Federation Quote to Apollo Federation 1. Building a graph should be declarative. With federation, you compose a graph declaratively from within your schema instead of writing imperative schema stitching code. 2. Code should be separated by concern, not by types. Often no single team controls every aspect of an important type like a User or Product, so the definition of these types should be distributed across teams and codebases, rather than centralized. 3. The graph should be simple for clients to consume. Together, federated services can form a complete, product-focused graph that accurately reflects how it’s being consumed on the client. 4. It’s just GraphQL, using only spec-compliant features of the language. Any language, not just JavaScript, can implement federation. #krish #graphQL #nestJS Support my work: https://www.paypal.com/paypalme/HelloKrish Github source: https://github.com/krish/graphql-federation-youtube-tutorial GraphQL Master class: https://www.youtube.com/playlist?list=PLD-mYtebG3X8mcXS3IfRWVy6H7-qKsAel NestJS: https://www.youtube.com/playlist?list=PLD-mYtebG3X-K97BlKyeQ-V-UyVmKBWkq Stay in touch: Facebook: https://www.facebook.com/Krish.Dinesh.Official/ Instagram : https://www.instagram.com/krish.dinesh.official/ twitter: https://twitter.com/krishantha (@Krishantha)