# GraphQL schema stitching

DevFeed: [GraphQL schema stitching](<https://devfeed.tech/articles/graphql-schema-stitching-23336.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/graphql-schema-stitching>)

Author: Sashko Stubailo

Published: 2017-09-07T00:22:00Z

Content type: article

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [API](<https://devfeed.tech/topics/api.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Structured-data](<https://devfeed.tech/topics/structured-data.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [backend](<https://devfeed.tech/tags/backend.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [schema](<https://devfeed.tech/tags/schema.md>)

## AI overview

This article explains GraphQL schema stitching, an approach for merging two or more GraphQL schemas into one endpoint so data from multiple GraphQL backends can be queried through a unified schema. It notes that the approach later led to Apollo Federation and recommends migrating to Federation for a more robust and scalable architecture.

## Source excerpt

Note: This post discusses Schema Stitching, an approach we explored that eventually led to the development of Apollo Federation. We recommend migrating to Federation for a more robust and scalable architecture. To get started, follow this migration guide and read this blog post for a real-world example of an organization benefiting from this migration.