Replies: 1 comment 1 reply
-
Interesting, it might be something we enable by config ? I think it can work, but I also thing we need to focus on the proper solution. Maybe me and you can meet sometime like we discussed and see if we can not finalize what you have started ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
GraphQL Federation is probably the most important reason to choose GraphQL over REST. I was wondering if it could be simplified even further.
ID
type field is by default equivalent to the containing type having a directive@key(fields = <fieldName>)
. This would allow many existing types to be extendable by other services.@extends
and@external
directives are optional. For some types there is no clear 'main' type, e.g. within the different bounded contexts of anOrder
, e.g. billing and fulfillment, none is clearly the 'core'. Only the type name and the id field may be common to all services and introducing a hierarchy may seem inappropriate; all services would be equally just extensions.Maybe I'll have to write such a federation gateway to prove that it's possible. What do you think?
Beta Was this translation helpful? Give feedback.
All reactions