Skip to content
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

Support Apollo Federation #374

Open
audkar opened this issue Jun 30, 2023 · 3 comments
Open

Support Apollo Federation #374

audkar opened this issue Jun 30, 2023 · 3 comments

Comments

@audkar
Copy link

audkar commented Jun 30, 2023

Summary

Support Apollo Federation. This requires to comply with the Federation Specification

Rationale

Federated superGraph allows composing multiple services. pg_graphql would be an ideal addition to the Apollo federation ecosystem as it allows to quickly add a Posgresql DB.

Also, Apollo provides a lot of advanced services for GraphQL schema maintenance.

Design

Federation Specification. I do not know pg_graphql implementation details. But seems that the most important needed functionalities (unique global nodeId resolution) already exist. Maybe that not much is needed to add @Key directives to nodeId and generate Entities union.

@olirice
Copy link
Contributor

olirice commented Jun 30, 2023

thanks, I'll have a look through the spec and report back

compatibility with secondary specs e.g. Apollo is a non-goal but if its something simple we can leave this open

@Tjerk-Haaye-Henricus
Copy link

Hey There 👋

is there any information on that ?
Are we able to use apollo federation with supabase ?

@olirice
Copy link
Contributor

olirice commented Jul 31, 2023

Federation is not currently being worked on

The subgraph spec is still niche, new, and pretty involved for us to implement

We may circle back in the future but for now its not something we want add first party support for

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants