Query Planning Across Subgraphs
When a client sends a query that spans multiple subgraphs, the router must create an execution plan. It determines which fields can be fetched independently and which fields require results from an earlier service call.
A simple query may require one subgraph first to identify an entity and another subgraph afterward to retrieve related fields.
This distributed execution introduces network latency and additional failure modes compared with a single server.