graphql-over-http
uWebSockets.js
graphql-over-http | uWebSockets.js | |
---|---|---|
12 | 32 | |
359 | 7,272 | |
0.6% | 1.3% | |
7.0 | 8.2 | |
about 1 month ago | about 2 months ago | |
JavaScript | C++ | |
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-over-http
-
What complaints do you have about GraphQL?
Another major pain is the fact that operation names and HTTP codes are often hidden in request bodies which makes it really hard to see what is going on in standard monitoring tools. It's possible to write some converter but it's beyond me why some people decided that requests which failed on the server respond with status 200. GraphQL spec doesn't define how it should behave, there's only a proposal (https://github.com/graphql/graphql-over-http)
-
GraphQL errors: the Good, the Bad and the Ugly
The GraphQL over HTTP specification states the following:
-
Websocket with socket.io or GraphQL subscriptions
However, if you are doing GraphQL subscriptions over Server Sent Events (HTTP) (which is currently not part of the GraphQL over HTTP specification), the data flow is only from server to client. So each operation must be a separate request, which should be no problem when using HTTP/2, as the browser connection limit is not hit so fast (There are also workarounds to this if you cannot ise HTTP/2).
-
Question about using fetch with a delete mutation
Complementary to the note, you can learn more about GraphQL over HTTP in the specification over here: https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md
-
Announcing GraphQL Yoga 2.0!
GraphQL-spec, GraphQL-over-HTTP: guarantees your GraphQL API to work with all existing GraphQL clients (Apollo, Relay, URQL, and more).
-
The Anatomy of a GraphQL Request
Note: While GraphQL can be done over almost any protocol, this article focuses on the most commonly used protocol GraphQL over HTTP. However, most knowledge can be transferred to other protocols such as GraphQL over WebSockets or other more exotic ones.
-
Is graphql payload usually like a string of query?
There is also the GraphQL over HTTP Specification repository https://github.com/graphql/graphql-over-http
-
GraphQL over SSE (Server-Sent Events)
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.
-
GraphQL over WebSockets
With no further ado - I humbly introduce graphql-ws. A coherent, feature-full, zero-dependency, plug-n-play, lazy, simple, server and client implementation of the new, security first GraphQL over WebSocket Protocol with full support for all 3 GraphQL operations: Queries, Mutations and Subscriptions. The protocol aims to be standardised and become a part of GraphQL with the help of the foundation’s GraphQL over HTTP work group.
-
How to handle errors that are from "context creation" ?
You could additionally also choose a specific HTTP code for that scenario (although that would contradict the official GraphQL over HTTP spec https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md).
uWebSockets.js
-
Building Real-Time Next.js Apps with WebSockets and Soketi
If you have never heard of Soketi, to give you a brief overview, it is a WebSocket server that was built on top of uWebSockets.js and has great compatibility with Pusher Protocol.
-
8 Best WebSocket Libraries For Node
# Clone the repo w/ submodules git clone --recursive https://github.com/uNetworking/uWebSockets.js.git # Cd into the folder cd uWebSockets.js # build make
- uWebSockets.js
-
Ask HN: How do you handle WebSocket connections reconnect problem?
have you tried https://github.com/uNetworking/uWebSockets.js/
-
I have done a full benchmark of a POST REST API on my computer: Node.js vs Fastify vs Express.js vs Deno vs Bun vs GO. Node.js is used WITH and WITHOUT clustering on 6-core I7 processor
If you'd like to test cluster mode, then use v19.3.0 as it described here https://github.com/uNetworking/uWebSockets.js/issues/593
- Simple, performant HTTP and WebSocket server using uWebSockets.js
- Millions of Active WebSockets with Node.js
-
KitaJs Survey - No runtime code, fast as bare metal and top level framework.
The fastest node framework is uWebSockets (as they claim, I didn't try it yet), so if Kita's goal is to maximize performance - you should check on it.
-
Can the performance of the clustered nodejs application compete with (or be better than) the performance of .NET Core-6-7?
I'm serving several hundred thousands queries per second from a single nodejs server (multithreaded) with this: https://github.com/uNetworking/uWebSockets.js/
-
Here is a fun question:
https://github.com/uNetworking/uWebSockets.js/ ^ this is the best for performance
What are some alternatives?
graphql-sse - Zero-dependency, HTTP/1 safe, simple, GraphQL over Server-Sent Events Protocol server and client.
fastify-websocket - basic websocket support for fastify
ws - Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js
graphql-yoga - 🧘 Rewrite of a fully-featured GraphQL Server with focus on easy setup, performance & great developer experience. The core of Yoga implements WHATWG Fetch API and can run/deploy on any JS environment.
pws - Just another simple, fast, and resilient open-source WebSockets server. 📣 [Moved to: https://github.com/soketi/soketi]
redwood - The App Framework for Startups
Socket.io - Realtime application framework (Node.JS server)
subscriptions-transport-ws - :arrows_clockwise: A WebSocket client + server for GraphQL subscriptions
jelly-actix-web-starter - A starter template for actix-web projects that feels very Django-esque. Avoid the boring stuff and move faster.