Orbit GraphQL

A cache server for your GraphQL API so you're ready for unexpected load

What?

1. Deploy it in front of GraphQL API, and it will start caching all requests passing through it.

2. Your cache gets automatically invalidated if anything changes in your application

3. Queries are only sent to origin if there is a cache MISS

Wait, why is it needed?

Because all GraphQL requests are on a single endpoint (usually POST) and resources are differentiated based on what your request body looks like, we can't use HTTP caching methods for them (say goodbye to etags, 304s, cache-control etc.)

Currently the ecosystem solves for the problem in two ways, client side cache or a server side cache.

Clients like urql can cache your API responses on the client side. Services like Stellate act as a cache proxy that does the same thing on the server side.

Orbit GraphQL is an open-source alternative to a tool like Stellate (server side cache for your GraphQL API).

This project is not ready for production traffic yet, but hopefully it will be soon (if you help)