Thoughts on the @defer/@stream directives RFC and schema stitching?

[maxbol]

Hi!

We are following the development of this RFC with great interest:

https://graphql.org/blog/2020-12-08-improving-latency-with-defer-and-stream-directives
https://github.com/graphql/graphql-spec/blob/main/rfcs/DeferStream.md

In our project, we are wrapping the graphql interface of a larger sales application in a business context-specific layer through stitching. The group that are maintaining the "inner" application are looking at methods to improve responsivity for their interface, and if they were to go with @defer/@stream once it's matured somewhat, we'd ofcourse want to be able to reap the same rewards on our end. But the way I see it, the stitchSchemas would have to be remodelled a bit to leverage this kind of async communication, so I'd be interested to know if there has been any discussions about handling this in the schema stitching project?

With kind regards,
Max

[ardatan]

See #1941 :)

[maxbol]

I seem to have commited the sin of asking a stupid question before doing a rudimentary search. :) Glad to see you are on top of it!