Skip to content

🕸️ GraphQL Federation Framework for any API services such as REST, OpenAPI, Swagger, SOAP, gRPC and more...

License

Notifications You must be signed in to change notification settings

BouyguesTelecom/graphql-mesh

This branch is 12 commits ahead of, 281 commits behind ardatan/graphql-mesh:master.

Folders and files

NameName
Last commit message
Last commit date
Dec 18, 2024
Jan 22, 2025
Jul 29, 2024
May 8, 2024
Nov 25, 2024
Dec 16, 2024
Jan 22, 2025
Jan 22, 2025
Dec 14, 2024
Nov 20, 2024
Dec 18, 2024
Jul 17, 2024
Nov 20, 2024
Nov 20, 2024
Jul 26, 2024
Jul 23, 2024
Jul 26, 2024
Dec 3, 2024
Nov 25, 2024
Mar 26, 2020
Oct 14, 2024
Dec 11, 2024
Sep 2, 2024
Dec 11, 2024
Jan 22, 2025
Dec 6, 2024
Jul 29, 2024
Dec 11, 2024
Nov 20, 2024
Jan 22, 2025

Repository files navigation

Mesh GIF

Created by The guild

 

GraphQL Mesh

GraphQL Federation framework for any API
Go to documentation

npm version CI Discord Chat code style: prettier

GraphQL Mesh is a GraphQL Federation framework and gateway for both GraphQL Federation and non-GraphQL Federation subgraphs, non-GraphQL services, such as REST and gRPC, and also databases such as MongoDB, MySQL, and PostgreSQL.

GraphQL Mesh allows you to use GraphQL query language to access data in remote APIs that don't run GraphQL (and also ones that do run GraphQL). It can be used as a gateway to other services or run as a local GraphQL schema that aggregates data from remote APIs.

The goal of GraphQL Mesh is to let developers easily access services that are written in other APIs specs (such as gRPC, OpenAPI/Swagger, OData, SOAP/WSDL, Apache Thrift, Mongoose, PostgreSQL, Neo4j, and also GraphQL) with GraphQL queries and mutations.

GraphQL Mesh gives the developer the ability to modify the output schemas, link types across schemas and merge schema types. You can even add custom GraphQL types and resolvers that fit your needs.

It allows developers to control the way they fetch data, and overcome issues related to backend implementation, legacy API services, chosen schema specification and non-typed APIs.

GraphQL Mesh is acting as a proxy to your data, and uses common libraries to wrap your existing API services. You can use this proxy locally in your service or application by running the GraphQL schema locally (with GraphQL execute), or you can deploy this as a gateway layer to your internal service.

How does it work?

The way GraphQL Mesh works is:

  1. Collect API schema specifications from services
  2. Create a runtime instance of fully-typed SDK for the services.
  3. Convert API specs to GraphQL schema
  4. Applies custom schema transformations and schema extensions
  5. Creates a Federation subgraph or a Federation-compatible supergraph

Getting started

Supported Source APIs

Schema Transformations

Contributions

Contributions, issues and feature requests are very welcome. If you are using this package and fixed a bug for yourself, please consider submitting a PR!

And if this is your first time contributing to this project, please do read our Contributor Workflow Guide before you get started off.

Code of Conduct

Help us keep GraphQL Mesh open and inclusive. Please read and follow our Code of Conduct as adopted from Contributor Covenant

License

GitHub license

MIT

About

🕸️ GraphQL Federation Framework for any API services such as REST, OpenAPI, Swagger, SOAP, gRPC and more...

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • TypeScript 82.8%
  • MDX 15.0%
  • Cypher 1.2%
  • JavaScript 0.9%
  • Shell 0.1%
  • Thrift 0.0%