Question: So what IS the difference between merge-schemas and stitch-schemas? #1894
-
|
Alluding to this line from the docs. On the surface they look the same except for stitch allows more config options. It is mentioned that the merge evolved from the But they look absolutely identical to me. Would be nice to get some clarity... BTW, absolutely stellar documentation, thanks for putting it together! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Schema Stitching creates a gateway/proxy schema on top of different independent subschemas so the parts of that schema are executed using GraphQLJS internally. This is useful to create an architecture like microservices. |
Beta Was this translation helpful? Give feedback.
Schema Stitching creates a gateway/proxy schema on top of different independent subschemas so the parts of that schema are executed using GraphQLJS internally. This is useful to create an architecture like microservices.
Schema Merging creates a new schema by merging the extracted type definitions and resolvers from them so there will be a single execution layer.
The first one keeps the individual schemas but the second one doesn't. So the first one is good for combining multiple remote GraphQL APIs but the second one is good for combining local schemas.