Tag: graphql-federation
-
GraphQL Federation where two services share data of a single shared schema
0 Really like the GraphQL Federation concept, where a gateway joins the data for clients. For example, imagine a library: Service A serves books from the library with title & ISBN property. Service B serves people, with a checkedOut list of books they have checked out, by ISBN. From what I can tell, though, there is…
-
graphene federation causing dependency issue
0 Trying to use Flask-GraphQL, graphene, starlette-graphene3 and graphene-federation to integrate python code with an existing graphql server. The code worked before trying to install graphene-federation. Other trys have meant pip unable to resolve dependencies. Packages before installing federation and graphql IDE runs locally. Flask==1.0.2 Flask-GraphQL==2.0.0 graphene==2.1.3 graphql-core==2.1 graphql-relay==0.4.5 graphql-server-core==1.1.1` If I install graphene-federation then…
-
Graphql federation vs schema stitching. When to pick one over the other
3 I’m new to both concepts so excuse me if it’s opinion-based. Currently, I’m looking at Apollo Federation and schema stitching provided by the graphql-tools package, though I guess it applies to similar packages. Could something like a table be created describing certain requirements/conditions to prefer one over the other? graphql graphql-tools graphql-federation Share Improve…
-
Merge an interface from one subgraph with a type from another subgraph using GQL Stitching
0 I have 2 services in my system, which both have their own subgraphs. Product Service, which is "smart" i.e. knows about different product types and Suggestions Service which is rather "dumb" i.e. only knows that there are some products, but nothing about specific types. So the 2 subgraphs look something like the following: Product…
-
Federated Graphql in case of list of items
0 I have defined Subgraphs as below and data is fetched from multiple sources Subgraph A type Query { getAllItems(type: String!) : AllItems } type AllItems{ type: String response: QueryResponse items: [Item!]! pageInfo: Page totalCount: Int } type Item @key(fields: "id") { val1: String val2: String id: ID! } SubgraphB type Item @key(fields: "id") @extends…
