Proposal - Mesh Modules

[Urigo]

Hi everyone and thank you for all the great feedback on the library!

This issue would act as an open discussion about a concept we want GraphQL Mesh to support:
Public GraphQL Mesh Modules.

• Mesh modules that can be installed and shared, inside a company and in the open
• Mesh modules that can be dependent on other modules and extend them

Because GraphQL Mesh create a Graph modules, together with implementation and an SDK that can run anywhere, as a community, we can start creating and sharing many SDKs like that.

Let's take for example the Stripe API. The Stripe API is not a GraphQL API.
But together with GraphQL Mesh, we are able to generate a GraphQL SDK on top of it.
That is something each of you can do locally today.
But once one of you did it, you can publish the Mesh config on Github and on npm.
Now anyone can simply install the Stripe GraphQL API.
They could even offer it for their users, without having any operational burden on them.

Dependency between modules:

Now, maybe you connected the Stripe Mesh API to you bank Mesh API.
You can now also share and publish that module, and now we have a Stripe+Bank Mesh modules everyone can collaborate and use.

An ongoing list of currently available Mesh Modules:

• Stripe
• JetBrains' YouTrack

What do we want from you:

1. What more modules you wish would be available from the community? Add anything you wish. Here are some places to take inspiration from - API.Guru
2. Name - is Mesh modules a good name or we can do better?
3. Registry - Should we just use npm?
4. We think the public and private Mesh modules should work the same. You should be able to have a registry of internal Mesh modules inside your company.
5. Share your own created modules?
6. Where should we display and manage all the public modules? Should we at all or just let the community evolve by itself?
7. Any other thoughts you might have
8. Could we create something that validates those schemas and tests the actual endpoints?
9. Crazy idea - Can this grow into something like a community data graph/semantic web/Web 3.0 thing? tell us why and why not :)

[marcus-sa]

1. A keycloak auth handler.
2. Should it really be called modules, when in fact it's called handlers in the mesh config?