# Handling the N+1 Problem Declaratively with Apollo Connectors

DevFeed: [Handling the N+1 Problem Declaratively with Apollo Connectors](<https://devfeed.tech/articles/handling-the-n-1-problem-declaratively-with-apollo-connectors-23354.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/handling-the-n1-problem-declaratively-with-apollo-connectors>)

Author: Lenny Burdette

Published: 2025-06-24T08:53:29Z

Content type: tutorial

Language: en

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

Topics: [Apollo Connectors](<https://devfeed.tech/topics/apollo-connectors.md>), [GraphQL](<https://devfeed.tech/topics/graphql.md>), [dataloaders](<https://devfeed.tech/topics/dataloaders.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [batching](<https://devfeed.tech/tags/batching.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [dataloaders](<https://devfeed.tech/tags/dataloaders.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [performance](<https://devfeed.tech/tags/performance.md>)

## AI overview

This tutorial explains how Apollo Connectors can address the N+1 query problem declaratively with Apollo Router 2.3 and Federation 2.11. It introduces the problem, compares the approach with DataLoaders, and describes how batching, scheduling, deduplication, and entity association work in Connectors.

## Source excerpt

With the release of Apollo Router 2.3 and Federation 2.11, Apollo Connectors can now avoid the dreaded N+1 query problem! You can make your API faster and more efficient by changing your Connectors to use the variable instead of the variable. If you want to learn more about the N+1 problem and how Connectors batching works internally, please read on! The N+1 query problem is a classic performance killer that sneaks up on developers.