Skip to content

fix: swap Client A and Client B to match the diagram #174

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

Merged
merged 1 commit into from
Sep 19, 2024
Merged

fix: swap Client A and Client B to match the diagram #174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 modules/ROOT/pages/subscriptions/scaling.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,8 @@ However, when trying to scale horizontally by adding more GraphQL servers, you m

image::subscriptions/diagram2.svg[title="Subscriptions with 2 servers"]

In this case, Client B is subscribed to one server.
However, when Client A triggers the mutation, it may query a different server.
In this case, Client A is subscribed to one server.
However, when Client B triggers the mutation, it may query a different server.

The change happens successfully in the database, and any client connected to the same server receives the subscription event.
However, Client A does **not** receive any update, as the server it's connected to does not get notified of any mutation.
Expand Down
Loading