Composite Schemas Announcement blog post #1696
Merged
+14
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@bignimbus is attempting to deploy a commit to the The GraphQL Foundation Team on Vercel. A member of the Team first needs to authorize it. |
bignimbus
commented
Apr 25, 2024
|
|
||
| In 2019, Apollo introduced GraphQL Federation as a way of splitting the task of building a GraphQL schema along team boundaries. It proposed a compelling alternative to prior techniques such as schema stitching and delegation, focussing on addressing the collaboration problems inherent in building a coherent schema within a large organization. Federation clearly filled a need and was adopted widely by platform engineers and API developers, a compelling way to compose microservices into a single access layer while retaining service boundaries and team ownership. Solutions from other vendors arose, tackling the same problems in similar ways but with different trade-offs, and some of the world’s largest enterprises have adopted these various patterns and are betting on GraphQL to solve some of their biggest pain points. | ||
|
|
||
| Adopting this style of collaboration has become a standard way of creating API platforms, with wide support from an array of vendors. Common patterns and best practices have been established around the various implementations and the underlying architecture has proven effective at scale. Today there are many approaches to collaborative GraphQL schema design, requiring different ways of defining the underlying schemas and composing the resulting architecture; for example Federation and Fusion take a … approach, whereas Mesh and Hasura take a … approach. API architects are having to make hard decisions early on in their projects, deciding which of the many patterns to follow. |
There was a problem hiding this comment.
This paragraph still needs content for ... - there's a suggestion in the Google Doc that I'll run with
Comment on lines
3
to
5
| tags: ["announcements"] | ||
| date: 2024-04-29 | ||
| byline: GraphQL Working Group |
There was a problem hiding this comment.
Is this the correct front matter / filename?
There was a problem hiding this comment.
file extension should be .mdx
Co-authored-by: Kamil Kisiela <kamil.kisiela@gmail.com>
bignimbus
changed the title
benjie
reviewed
May 14, 2024
|
@benjie or @dimaMachina - the Vercel check isn't passing, but is this OK to merge? |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
benjie
reviewed
May 16, 2024
benjie
approved these changes
May 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See also: graphql/composite-schemas-wg#157