-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] Apollo federation #299
Comments
Hi @remorses, Yep, this could be a cool feature. And it is well suited to be in a Tartiflette-plugin-apollo-federation. |
Yes i will work on it. Do you know if there is a way to access the complete sdl string from the resolver arguments? The spec requires that |
Hum, that why I have to take time to read this spec, There are somethings that are not doable rightnow, I need to find what is needed in the Engine itself so you could implemented the Plugin and we can implement the Engine/Schema interface for you to use. |
I made a basic implementation at https://github.com/remorses/tartiflette-plugin-apollo-federation |
Yeah we'are working on this rigth now at the office. As it is a requirement for a lot of coool features, we wanna do it right, that's why we're taking some time to do it. I'll ping you on the PR when it will be ready to show and comment. It's coming soon. |
I'm interested in this feature too. Are there any updates? Thanks |
@jugdizh the plan is to have this possible in v2. RN @Maximilien-R is working on a refactoring of the validation side of the schema and query which will be the starting point of the v2 branch in which we will completly rework the schema side of tartiflette to enable these kind of feature. I think, we'll be there for 2021. |
@abusi Do you have an ETA for the V2 version containing this feature? We are evaluating it and we would use something of maintained because used in production. Unfortunately, graphene seems dead. |
@ca-simone-chiorazzo Sadly, V2 will only contains tools that would help us make this, V2 should happen in 2021, but I can't get you an ETA as I'm not focused on it RN. If you really need it, and are interested in tartiflette, feel free to submit any PR, i'll gladly review it. |
@abusi Thank you for the clarification! |
Excited to have federation support! |
@gc-ss Sadly, the development speed of tartiflette is not moving fast. Appolo federation work hasn't started :D, sorry to disapoint, I don't really know if we're gonna do it :/ |
I really appreciate providing this feedback! |
@gc-ss I'm a little bit disconnected from the GQL world, I know we want to implem GQL-2021 (since we already have some of the feature, we don't miss a lot), but is |
I won't say I am by any means connected to the GQL world either but I am looking for a framework that lets me stitch together various independent services (subgraphs) while exposing them through one API Gateway (supergraph) Whether this is done using apollo's federation solution or something else, is secondary to having any support for it at all. For example, taking a stab at https://github.com/movio/bramble or https://github.com/gmac/schema-stitching-handbook is a welcome pursuit 👍 |
Hum, tartiflette doesn't support schema stitching, in the sense that tartfilette does need the complete schema to work. But on a complete schema, a resolver can query a remote service without any problem. |
The spec of Apollo federation allows to build graphql servers that can be composed one with another, i think it would be cool to implement the spec in tartiflette.
The implementation consist in implementing the following types, then the schema can be integrated in an apollo federation gateway
The spec is here
Here is an attempt of implementing it for graphene
The text was updated successfully, but these errors were encountered: