Imagine having a project where multiple teams are involved in each team:
Cooperating on a huge project schema might be confusing…
Schema stitching is a process of merging multiple GraphQL schemas into one that can be queried. It’s an incredibly useful approach when it comes to building projects that require having both, unified & transparent access to a data split across multiple APIs (even without understanding where exactly it’s located). It can be also used to customize an existing GraphQL API like adding custom resolvers or overriding existing ones of third-party GraphQL service or adding more fields to an existing type whose data comes from another data source.
Although putting two schemas into one in a way where there are no name collisions seems quite simple, but that’s not a real schema stitching. What we want to achieve is one consistent schema, merged from multiple underlying GraphQL APIs. That’s a way more difficult, but what if a told you that there is an app for that?
The latest release of GraphQL Editor introduced an easy way to collaborate on schemas. All we need to do is:
1. Add two or more schemas to our account - you can load them from URL or .gql file
… and that’s it!
As long as we have managed to avoid conflicts between our underlying schemas, we should have access to all their elements in our newly generated project 👌
The GraphQL Editor is a supportive tool for both advanced GraphQL users as well as those taking their first steps with GraphQL APIs. Our all-in-one development environment for GraphQL will help you build, manage & deploy your GraphQL API much faster thanks to dozens of built-in micro features. Its graphical interface will also fix communication within your product team. Visualization is the key!