graphql-ws
GraphQL Kotlin
Our great sponsors
graphql-ws | GraphQL Kotlin | |
---|---|---|
17 | 2 | |
1,103 | 1,442 | |
- | 2.2% | |
9.0 | 8.6 | |
11 days ago | 3 days ago | |
TypeScript | Kotlin | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
graphql-ws
-
GraphQL Subscriptions: Why we use SSE/Fetch over Websockets
There is already a JavaScript implementation for server + client with support for multiplexing from the same maintainer of graphql-ws: graphql-sse
-
how it subscription work on the apollo server?
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.
-
Advice on using graphql-ws with Apollo/React
That said, I feel so close to success that I can't quite give up. I am using graphql-ws as I understand this to be the new standard implementation of GraphQL Subscriptions. However, of course, Apollo subscriptions have not been updated to implement this. So, looking at the Recipes over on the graphql-ws documentation I have found the guide for using Apollo client. However as I am new to Apollo, it is using a lot of terms I am unfamiliar with.
-
GraphQL Subscriptions and Mikro-Orm in 2021
Okay but seriously, if you've fallen down the rabbit hole of Apollo docs pointing you towards one library (subscription-transport-ws) which then points you to another (graphql-ws) , and so on and so forth, then hopefully this helps pull you out.
-
How does a client know if the server managing its subscription goes offline? (Multiple instances)
The most common protocol used today for subscriptions is the Apollo websocket protocol.
-
Graphql Subscriptions w/o apollo
GraphQL subscriptions are just web sockets. You can check graphql-ws package if you want something without Apollo dependency. Though I don't understand why you want to not depend on it in the first place.
-
GraphQL Tools V8 - Stitch Federation Services
New GraphQL-WS ✔️
-
Subscriptions and Live Queries - Real Time with GraphQL
The interesting thing is that we can use any transport for delivering the results to client. The most popular implementation (as mentioned before) is subscriptions-transport-ws. Unfortunately, since it is poorly maintained, the GraphQL Working Group came up with a new implementation over WebSockets, graphql-ws.
-
GraphQL over WebSockets
Okay, so, how do I use WebSockets to add support for the GraphQL subscription operation? Doing a basic Google search, you’d be faced with a single solution, namely subscriptions-transport-ws. Looking through the repository, checking recent comments, reading through the issues and open PRs - might have you notice the abundance of bugs and their security implications. A summary can be found here.
-
I need a little help implementing user online status tracking with Apollo/GraphQL.
Have you thought about using graphql-ws instead? It uses the new graphql-transport-ws protocol which also has an open RFC that is discussed in the GraphQL working Groups.
GraphQL Kotlin
-
I am considering switching to TypeScript on a personal project
Their client framework officially supports ktor client https://github.com/ExpediaGroup/graphql-kotlin/tree/master/clients/graphql-kotlin-ktor-client while their schema generator seems to be just framework-independent jvm library https://github.com/ExpediaGroup/graphql-kotlin/tree/master/generator/graphql-kotlin-schema-generator And you could use their gradle plugin as described here https://github.com/ExpediaGroup/graphql-kotlin/tree/master/plugins/graphql-kotlin-gradle-plugin which would make the whole thing a breeze I guess :)
-
GraphQL Kotlin 4.0.0 is out!
GraphQL Kotlin consists of a number of libraries that aim to simplify the running of GraphQL servers and clients using Kotlin. It’s been over 10 months since the last major release of graphql-kotlin and after hundreds of commits and numerous pre-releases, we are pleased to announce the 4.0.0 release!
What are some alternatives?
subscriptions-transport-ws - :arrows_clockwise: A WebSocket client + server for GraphQL subscriptions
apollo-server - 🌍 Spec-compliant and production ready JavaScript GraphQL server that lets you develop in a schema-first way. Built for Express, Connect, Hapi, Koa, and more.
graphql-helix - A highly evolved GraphQL HTTP Server 🧬
ktor - Framework for quickly creating connected applications in Kotlin with minimal effort
ws - Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js
apollo-android - :robot: A strongly-typed, caching GraphQL client for the JVM, Android, and Kotlin multiplatform.
KGraphQL
graphql-sse - Zero-dependency, HTTP/1 safe, simple, GraphQL over Server-Sent Events Protocol server and client.
react-relay - Relay is a JavaScript framework for building data-driven React applications.
better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.
fastify-websocket - basic websocket support for fastify
graphql-tools - :wrench: Build, mock, and stitch a GraphQL schema using the schema language