graphql-jit
nestjs-graphql
Our great sponsors
graphql-jit | nestjs-graphql | |
---|---|---|
10 | 1 | |
1,024 | 0 | |
0.3% | - | |
6.7 | 0.0 | |
30 days ago | over 2 years ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | 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-jit
-
How much overhead does nodejs graphql have?...
In the end like all performance questions you'll have to measure it. Persisted queries, and even more extreme approaches, like a GraphQL JIT (https://github.com/zalando-incubator/graphql-jit) can remove a lot of the overhead.
-
PSA don't use Datadog agent in a GraphQL project
We faced something similar. To improve GraphQL performance, we use graphql-jit. We turned off all other tracing that datadog turns on by default. Then, we then wrote a custom tracer to connect graphql-jit to dd-trace. Hopefully this same pattern works for you!
-
Hacker News top posts: May 19, 2022
GraphQL JIT – GraphQL execution using a JIT compiler\ (0 comments)
-
GraphQL JIT – GraphQL execution using a JIT compiler
https://github.com/zalando-incubator/graphql-jit#compile-a-q...
so I guess the difference is instead of having totally generic functions that parse the query every time, instead you can call a factory function up front to get a specialised function for a particular query
and V8 JIT can make that faster
-
Manifest v3 in Firefox: Recap and Next Steps
JS has always been special & excellent because it allows multiphase programming. That one coild just add more code has been unique versus the world of statuc languages, where maybe youcd have some tool to generate stubs for Thrift or gRPC, then compule that in to your program. Which works ok, if and only if you know ahead of time what schemas you might need. Im these cases, you have to give up on stub code & start using more interprtted systems.
The advantages in js have been colossal, often an easy order of magnitude win to compile selectors & queries & other fast inner loop bits into jit compiled code versus having userland interpretters. Some of thd rete engines enjoy this. Just today there's graphql-jit. https://github.com/zalando-incubator/graphql-jit/blob/main/s...
Everything you say is full of doubt & scorn & skepticism. I just cant imagine living im such a world where each system had to know fully well ahead of time each type of data it might want to interact with, might have to have that precompiled & baked in. Thatcs a shitty miserable world that looks like the hell JS plucked us out of, by being a flexible, dynamic language that could load in routines & change it's behavior over time. Screw that dark hell world.
-
Introducing Envelop - The GraphQL Plugin System
By using useParserCache we make sure to parse every unique operation only once. By using useValidationCache we make sure to validate every unique operation only once. By using useGraphQLJit we replace the default execute function with a just-in-time implementation.
-
GraphQL - Diving Deep
One thing to understand is that, if you are using Node.js graphql-js would typically be the underlying implementation of all libraries and ultimately everything would get converted to JS/TS objects typically an AST ultimately making all these as abstractions on top of the existing way to define schemas. Note that the implementation can differ a bit in other languages or even within Node.js if you are using other ways of implementation like graphql-jit
-
Introducing Envelop: The GraphQL Plugin System
Could you provide more context? the GraphQLJit plugin is a lightweight wrapper around graphql-jit. Could you share your previous datadog/graphql setup? Would love to dig in and find a proper solution!
-
Benzene: Fast, minimal, agnostic GraphQL Libraries
Customizable runtime. Use custom GraphQL implementation such as graphql-jit or rolling our own for performance and cutting-edge features.
nestjs-graphql
-
Introducing Envelop - The GraphQL Plugin System
During that process, we also start to work with other frameworks and support them with that: Loopback, NestJS, Parse, Apollo Server and others.
What are some alternatives?
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 🧬
parse-server - Parse Server for Node.js / Express
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
envelop - Envelop is a lightweight library allowing developers to easily develop, share, collaborate and extend their GraphQL execution layer. Envelop is the missing GraphQL plugin system.
graphql-js - A reference implementation of GraphQL for JavaScript
webextensions - Charter and administrivia for the WebExtensions Community Group (WECG)
redwood - The App Framework for Startups
graphql-public-schema-filter - Filter your GraphQL graph into a subgraph. Code-first & SDL-first!