# Using Apollo Link to Handle Dependent Queries

DevFeed: [Using Apollo Link to Handle Dependent Queries](<https://devfeed.tech/articles/using-apollo-link-to-handle-dependent-queries-23559.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/using-apollo-link-to-handle-dependent-queries>)

Author: Aryan Goharzad

Published: 2020-04-13T18:59:00Z

Content type: tutorial

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [apollo-server](<https://devfeed.tech/topics/apollo-server.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [apollo](<https://devfeed.tech/tags/apollo.md>), [apollo-client](<https://devfeed.tech/tags/apollo-client.md>), [backend](<https://devfeed.tech/tags/backend.md>), [context](<https://devfeed.tech/tags/context.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [server](<https://devfeed.tech/tags/server.md>)

## AI overview

This tutorial explains how to handle dependent GraphQL queries when a screen needs data from multiple related queries. It compares updating the GraphQL server, passing one query's result to another, and using Apollo Link to pass values automatically.

## Source excerpt

If you're using GraphQL and Apollo to build an app, sooner or later you'll run into cases where there are queries that depend on each other. In an ideal world, each screen would use just one query to fetch all of the information it needs. However, in the real world, you may not always be able to accommodate your front-end needs in the GraphQL backend. Imagine you're creating a social network app for users from various planets.