Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Updated tags from 'announcements' to 'blog'.
Remove unused image and clean up markdown formatting.
for higher-fidelity representation of rendered content
bignimbus
commented
Feb 19, 2026
|
|
||
| * We are powering multiple client platforms across multiple business domains. | ||
| * We leverage the [server-driven UI (SDUI)](https://www.apollographql.com/docs/technotes/TN0032-sdui-basics/) architectural pattern to minimize client-side logic and facilitate consistency between client platforms. | ||
| * We use [GraphQL federation](https://www.apollographql.com/docs/federation/) to hydrate clients with data via a unified GraphQL API that aggregates numerous microservices. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| * We use [GraphQL federation](https://www.apollographql.com/docs/federation/) to hydrate clients with data via a unified GraphQL API that aggregates numerous microservices. | |
| * We use [GraphQL federation](https://graphql.org/resources/federation/) to hydrate clients with data via a unified GraphQL API that aggregates numerous microservices. |
|
|
||
| Before we answer this question, let’s first delineate the larger context. | ||
|
|
||
| More and more organizations are adopting a [GraphQL-native approach](https://www.apollographql.com/docs/technotes/TN0037-api-gateways/#graphql-native). This unlocks the ability to *codify* the contract between data consumers and data providers. What used to be a polyglot system of BFFs, with unpredictability and a lack of standards between systems, has been modernized and replatformed into massive unified APIs all feeding into a single supergraph endpoint. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| More and more organizations are adopting a [GraphQL-native approach](https://www.apollographql.com/docs/technotes/TN0037-api-gateways/#graphql-native). This unlocks the ability to *codify* the contract between data consumers and data providers. What used to be a polyglot system of BFFs, with unpredictability and a lack of standards between systems, has been modernized and replatformed into massive unified APIs all feeding into a single supergraph endpoint. | |
| More and more organizations are adopting a [GraphQL-native approach](https://konghq.com/solutions/api-management-graphql). This unlocks the ability to *codify* the contract between data consumers and data providers. What used to be a polyglot system of BFFs, with unpredictability and a lack of standards between systems, has been modernized and replatformed into massive unified APIs all feeding into a single supergraph endpoint. |
|
|
||
| More and more organizations are adopting a [GraphQL-native approach](https://www.apollographql.com/docs/technotes/TN0037-api-gateways/#graphql-native). This unlocks the ability to *codify* the contract between data consumers and data providers. What used to be a polyglot system of BFFs, with unpredictability and a lack of standards between systems, has been modernized and replatformed into massive unified APIs all feeding into a single supergraph endpoint. | ||
|
|
||
| Unified data APIs have unlocked a more intelligent architecture that allows a [demand-oriented](https://www.apollographql.com/docs/technotes/TN0027-demand-oriented-schema-design/) approach. This means that product teams, as well as specific client consumers, can ask for just the data they need. |
Contributor
Author
There was a problem hiding this comment.
If there's an authoritative community resource for this, we should update to point to that URL. Otherwise, I think it's okay to leave this as-is
Comment on lines
+229
to
+242
| ## About the Authors | ||
|
|
||
| **![][image34]** | ||
| **Amanda Olsen** | ||
| Senior Frontend Engineer | ||
|
|
||
| Amanda has a passion for efficiency and high-level thought. As a Frontend Engineer for 17+ years, she has had to learn to think from the user’s perspective while coding/building systems. What threw a curveball into all of this was the rise of GraphQL and also of design systems, occurring at about the same time. She scoured the internet for how to appropriately relate these two and came up empty handed. Upon meeting Sam at the GraphQL Summit, many concepts came together and they decided to construct this article, which would have been the article she was looking for. | ||
|
|
||
| ![][image35] | ||
| **Sam Combs** | ||
| Senior Full-Stack Engineer | ||
|
|
||
| Sam was exposed to computers at a very young age, sparking a passion that he can now proudly call his livelihood. He cut his teeth as a full stack developer building organic farm management solutions which gave him experience in working with large data sets and creating UIs for non-technical users. Introduced to GraphQL in 2018, Sam currently works at Xolvio, the official Apollo GraphQL professional services partner, working with large enterprises like Wayfair, Ford Credit, and more. | ||
|
|
Contributor
Author
There was a problem hiding this comment.
We don't typically do "About the Authors" on GraphQL.org posts
Suggested change
| ## About the Authors | |
| **![][image34]** | |
| **Amanda Olsen** | |
| Senior Frontend Engineer | |
| Amanda has a passion for efficiency and high-level thought. As a Frontend Engineer for 17+ years, she has had to learn to think from the user’s perspective while coding/building systems. What threw a curveball into all of this was the rise of GraphQL and also of design systems, occurring at about the same time. She scoured the internet for how to appropriately relate these two and came up empty handed. Upon meeting Sam at the GraphQL Summit, many concepts came together and they decided to construct this article, which would have been the article she was looking for. | |
| ![][image35] | |
| **Sam Combs** | |
| Senior Full-Stack Engineer | |
| Sam was exposed to computers at a very young age, sparking a passion that he can now proudly call his livelihood. He cut his teeth as a full stack developer building organic farm management solutions which gave him experience in working with large data sets and creating UIs for non-technical users. Introduced to GraphQL in 2018, Sam currently works at Xolvio, the official Apollo GraphQL professional services partner, working with large enterprises like Wayfair, Ford Credit, and more. |
Contributor
Author
There was a problem hiding this comment.
Adding some notes. I think linking to some Apollo docs is okay if it's the most authoritative resource for the relevant concept. I tried to find sufficient replacements to ensure that we're linking to (ex: graphql.org has a GraphQL Federation page)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #
Description