graphql-over-http
apollo-server
graphql-over-http | apollo-server | |
---|---|---|
12 | 66 | |
359 | 13,670 | |
0.6% | 0.2% | |
7.0 | 9.1 | |
about 1 month ago | about 16 hours ago | |
JavaScript | TypeScript | |
MIT License | MIT License |
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).
apollo-server
-
React Server Components Example with Next.js
Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and Iām curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.
-
Building Scalable GraphQL Microservices With Node.js and Docker: A Comprehensive Guide
There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.
-
Launch HN: Serra (YC S23) ā Open-source, Python-based dbt alternative
As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.
[1] https://github.com/apollographql/apollo-server/blob/9817bc47...
-
Who moved my error codes? Adding error types to your GoLang GraphQL Server
While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, weāve got a strong indication we took the right approach.
-
Zero to Serverless Car Insurance - Part 2
GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.
- How can i do query directives or executable directives?
-
How we migrated to Apollo Server 4
After some head-scratching, I opened an issue on Apollo Serverās GitHub repository. There, Apollo Server contributor @āglasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Serverās context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:
-
why would a developer choose nodejs over c#.net for backend?
Apollo as a middleware in Express.js, actually.
-
Using Postman and Postman Interceptor to authenticate a session cookie based GraphQL API
Apollo Server 3 Cookie Issue #5775
-
Custom API server with basic CRUD ā Apollo, GraphQL & MongoDB
Lastly, instead of writing our API core ourselves, we'll be using the star of this episodeā---āApollo Server (a.k.a. GraphQL server). It has detailed documentation available here.
What are some alternatives?
graphql-sse - Zero-dependency, HTTP/1 safe, simple, GraphQL over Server-Sent Events Protocol server and client.
mercurius - Implement GraphQL servers and gateways with Fastify
fastify-websocket - basic websocket support for fastify
graphql-mesh - The Graph of Everything - Federated architecture for any API service
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.
nestjs-graphql - GraphQL (TypeScript) module for Nest framework (node.js) š·
redwood - The App Framework for Startups
subscriptions-transport-ws - :arrows_clockwise: A WebSocket client + server for GraphQL subscriptions
express-graphql - Create a GraphQL HTTP server with Express.
ws - Simple to use, blazing fast and thoroughly tested WebSocket client and server for Node.js
graphql-ws - Coherent, zero-dependency, lazy, simple, GraphQL over WebSocket Protocol compliant server and client.