apollographql / apollographql/federation

Add the option of forwarding federated queries

Open
#391 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
727
Forks
276
Avg merge
1h 47m
Merged PRs (30d)
1

Description

For a development scenario it would be convenient if the federation service could act as a middle man for other underlying federation services. The idea is that a developer could setup the following

1. A Federation Gateway on their system
2. One of the underlying services on their system

The gateway would then hit a pre-existing gateway containing the rest of the graph, overriding the service that they are running locally. This would allow developer to not need to run the full suite of services on their machine in order to work on one. This would also need to be an opt-in flag due to the potential security implications of this setup.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the federation gateway’s handling of incoming federated queries and how configuration flags are defined; the issue names no files or tests. Clarify the opt-in forwarding flow between the local gateway, underlying service, and pre-existing gateway, then define tests for forwarding, the default-disabled behavior, and the security boundary.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
backend-api-design, distributed-systems, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.