GraphQL Schema stitching

With Schema stitching, developers can create a unified GraphQL schema from multiple underlying GraphQL APIs. This gives us the benefit of reducing multiple data queries for our data in a single request from one schema.
In this episode, Jeremy chats with the author of Hot Chocolate, Michael Staib, about how .NET developers can implement GraphQL schema stitching with Hot Chocolate.
[01:57] - What is schema stitching about?
[06:00] - Schema stitching with Hot Chocolate
[09:08] - Querying with Banana Cake Pop
[10:16] - Setting up the GraphQL Gateway
[13:56] - Customizing the schema
[20:42] - Merging related schemas
Schema Stitching Examples
github.com/ChilliCream/hotcho...
Getting started with GraphQL and HotChocolate
channel9.msdn.com/Shows/On-NE...
Create web APIs with ASP.NET Core
docs.microsoft.com/en-us/aspn...

[@BenHayat]

GraphQL is the future of data shaping. To top that off, Schema Stitching takes it to another level. This is my future direction of building enterprise grade application.
Well done Jeremy & Michael.
MSFT should invest in this company to give it a boost.

[@etzumahkaya9583]

Grettings from Chile coleagues, great job HC

[@henningms]

We use Apollo Federation and Stitching in our projects (nodejs), but this looks awesome. Will have to try it out for sure!

[@Rajesh-wc3co]

Hi Jeremy and Mike, I am a great fan of you both, technically learned REST and GraphQL seeing both of your videos.
I have few questions below. Your answer will be greatly appreciated.
1. How to solve the n + 1 problem when implementing schema stitching between micro services based of GraphQL
2. How to implement stitchings with a GraphQL Gateway and Backend REST/ODATA Api

[@alfredoperez2420]

I am even not a Junior software engineer yet, but I never used more than one database, I have used Hot Chocolate 10 for a few projects, University and hobbies, I want to try this feature migrating a hobby project, having multiple databases, and see if it can get some extra performance besides of upgrading it to .NET 5, thanks Michael, ChillieCream is doing well, blessings!

[@Endomorphism]

Cool demo
It would make much more sense if these schema files were in gateways.
Why bcs its the aggrigate project.

[@michaelstaib860]

We support multiple approaches, you can have a centralized approach as well as a fully federated approach with hot-reload. Have a look at our examples:
github.com/ChilliCream/hotchocolate-examples/tree/master/misc/Stitching

[@christianfredh]

Nice demo, will check this out! But...can't really devlop services independently if you need to know the details of one another. One Stitching.graphql in gateway-project would be better at first glance and do the trick as well, right?

[@michaelstaib860]

We support multiple approaches, you can have a centralized approach as well as a fully federated approach with hot-reload. Have a look at our examples:
@t

[@christianfredh]

@@michaelstaib860 Thanks for the reply! Good to hear, will check out the examples.