graphql-sse VS graphql-zeus

The GraphQL over SSE in its simplest form IMHO does not require an additional client library. Setting up a subscription in the browser is as simple as doing the following:

There is already a JavaScript implementation for server + client with support for multiplexing from the same maintainer of graphql-ws: graphql-sse

Actually WebSocket is not the only protocol for executing GraphQL subscriptions. There is also a graphql-over-sse protocol, which is much more lightweight, and uses Server Sent Events. A popular implementation of it is the graphql-sse library, which is maintained by the same person as graphql-ws. The setup and API of both libraries is pretty similar.

graphql-sse is a reference implementation of the GraphQL over Server-Sent Events Protocol aiming to become a part of the GraphQL over HTTP standard.

When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.

You can think of GraphQL Zeus as Prisma for the frontend: it writes GraphQL queries out of JavaScript objects and produces the proper return types.

graphql-zeus: You write your graphql queries using a JavaScript object like syntax. Looks cool, but I think it's too big of a burden on the team to have to give up writing queries using graphql-tag/gql.

https://github.com/graphql-editor/graphql-zeus generates subscription code and in generated code you'll find simple apiSubscription function you can use/copy

You can do this with GraphQL too:

https://genql.vercel.app/

https://github.com/graphql-editor/graphql-zeus

I did a 5 min talk about these newer breeds of codegen tools (where it's a single client SDK that does automatic return type inference based on the input args), it's really neat:

https://www.youtube.com/watch?v=7n3MeMFHiMk