# zalando-incubator/graphql-jit

GraphQL execution using a JIT compiler

Repository: https://github.com/zalando-incubator/graphql-jit
Canonical: https://ross.abutalabs.com/products/graphql-jit
Homepage: https://try-graphql-jit.boopathi.in/
Language: TypeScript
License: NOASSERTION
License Family: other
Last push: 2026-09-02T10:22:32+00:00

## Health v2 (maintenance only)
Score: 89/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 100, release rhythm 68, longevity 100
- inputs: {"age_days": 2883, "days_push": 0, "days_rel": 0, "gap_med": 339.5, "n_releases_24m": 3}
- flags: no_license
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1084, forks 64 (observed 2026-09-03T02:15:20.838456+00:00)

## What it is
A TypeScript library that compiles GraphQL queries into optimized JavaScript functions using V8's JIT compilation, serving as a drop-in alternative to graphql-js execution with significantly better performance. It supports the June 2018 GraphQL spec including queries, subscriptions, and resolvers, with some limitations around computed properties and Promise handling.

## Use cases
- speed up GraphQL query execution in Node.js servers
- replace graphql-js execute for better throughput
- compile GraphQL documents into reusable functions
- run GraphQL subscriptions with lower overhead
- benchmark GraphQL execution performance
- serve high-traffic GraphQL APIs with lower latency

## When to choose
- your GraphQL server is CPU-bound on query execution and graphql-js is a bottleneck
- you need many resolvers executed per query at high request rates
- you want a mostly drop-in replacement for graphql-js execution with the same schema tooling
- you can precompile queries at startup or cache compiled queries per document

## When to avoid
- you rely on default field resolvers returning Promises for computed properties without explicit resolvers
- you need the very latest GraphQL spec features beyond June 2018
- your workload is dominated by I/O rather than execution overhead
- you depend on graphql-js internals or custom execution semantics that jit does not replicate

## Facets
- artifact type: library
- maturity: active
- function: graphql, compiler, interpreter, middleware
- domain: web-development, apis, backend, developer-tools, performance
- platform: -
- tags: graphql-execution, jit-compiler, graphql-js-alternative, query-execution, v8-optimization, high-performance, nodejs, javascript, typescript

## Member repositories
- zalando-incubator/graphql-jit (main) score 89

## Provenance
- Observed fields: from GitHub, fetched 2026-09-03T02:15:20.838456+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:50:11.570840+00:00, confidence not recorded.
  - readme: https://github.com/zalando-incubator/graphql-jit (fetched 2026-09-03T02:15:20.838456+00:00, sha 74732f244463)
  - homepage: https://try-graphql-jit.boopathi.in/ (fetched 2026-08-29T12:52:58.436767+00:00, sha be06a53013a7)
  - registry_npm: https://registry.npmjs.org/graphql-jit (fetched 2026-08-29T12:52:58.445757+00:00, sha 5767f8b86f02)
- Data as of 2026-08-30T08:39:29.467469+00:00.