Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed typos in the schema federation docs. #4544

Merged
merged 3 commits into from
Dec 13, 2021
Merged

Fixed typos in the schema federation docs. #4544

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2f38932
fix typo
yohosuff Dec 13, 2021
becbbb6
fix another typo
yohosuff Dec 13, 2021
6f6b04f
Merge branch 'main' into patch-1
michaelstaib Dec 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/src/docs/hotchocolate/distributed-schema/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ type Address {
In the scenario of schema stitching, the configuration of the gateway schema is on the gateway itself.
The gateway pulls the schema from the downstream services and can be extended with SDL.
The benefit of this approach is that no configuration on the downstream services is needed.
With this approach, it is possible to also stitch thrid party GraphQL services.
With this approach, it is possible to also stitch third party GraphQL services.

Gateway:

Expand All @@ -86,7 +86,7 @@ graph TD;
The major difference between schema federation and schema stitching is where the extensions are stored.
In the federated approach, the schema extensions are defined on the federated service.
The domain services push the schema on a cache (like Redis).
The gateway is subscribed to changed from this cache and can hot reload the schema if the configuration of a domain service changes.
The gateway is subscribed to changes from this cache and can hot reload the schema if the configuration of a domain service changes.
It is also possible to set up federations in a pull setup.
In this setup, the downstream services expose a field on their schema to fetch the stitching information.
The gateway then fetches the federation information from the downstream service on startup.
Expand Down