Skip to content

Commit

Permalink
Hive Gateway supports only SSE for subscriptions (#5669)
Browse files Browse the repository at this point in the history
  • Loading branch information
enisdenjo authored Oct 11, 2024
1 parent 2031cb6 commit 2104901
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions packages/web/docs/src/pages/docs/gateway/subscriptions.mdx
Original file line number Diff line number Diff line change
@@ -16,6 +16,10 @@ protocols:
- [GraphQL over WebSocket](https://github.com/graphql/graphql-over-http/blob/main/rfcs/GraphQLOverWebSocket.md)
- [HTTP Callback](https://www.apollographql.com/docs/router/executing-operations/subscription-callback-protocol/)

Clients connecting to the Hive Gateway must use the:

- [GraphQL over SSE](https://github.com/graphql/graphql-over-http/blob/main/rfcs/GraphQLOverSSE.md)

## Example

We'll implement two
@@ -174,9 +178,9 @@ Now simply start Hive Gateway with:
hive-gateway supergraph
```

Downstream clients are still subscribing to Hive Gateway gateway through any supported subscriptions
protocol, but upstream Hive Gateway will use long-living WebSocket connections to the "products"
service.
Downstream clients are subscribing to Hive Gateway gateway through the
[GraphQL over SSE protocol](https://github.com/graphql/graphql-over-http/blob/main/rfcs/GraphQLOverSSE.md),
but upstream Hive Gateway will use long-living WebSocket connections to the "products" service.

<Callout>
WebSocket for communications between Hive Gateway and subgraphs are suboptimal compared to other

0 comments on commit 2104901

Please sign in to comment.