We have a two tier architecture with Supergraph served by Subgraphs integrating into REST APIs. We are not planning to use connectors for the time being. We want to keep the backend swagger’s data model to the GraphQL Schema / SDL in sync. Has someone used any particular approach to solve for this problem?
Hi @souvik can you perhaps share an example of how tightly you want to keep your REST and Graph APIs in sync?
I ask because we often see advantages to adjust the naming and even the shape of data exposed at the graph tier from the lower level REST api naming/shape. This is why Connectors come with transforms to allow you to rename fields.
Given we are adopting an industry data model, the nomenclature/ taxonomy will remain same across graphs and REST. For the rest, if we have custom data models, I am not worried about the end to end keeping this in sync. Good question, thanks for the clarifying ask