# Batching Client GraphQL Queries

DevFeed: [Batching Client GraphQL Queries](<https://devfeed.tech/articles/batching-client-graphql-queries-23234.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/batching-client-graphql-queries>)

Author: Jake Dawkins

Published: 2018-09-19T23:33: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-client](<https://devfeed.tech/topics/apollo-client.md>), [React](<https://devfeed.tech/topics/react.md>), [client](<https://devfeed.tech/topics/client.md>)

Tags: [apollo-client](<https://devfeed.tech/tags/apollo-client.md>), [batching](<https://devfeed.tech/tags/batching.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [network](<https://devfeed.tech/tags/network.md>), [performance](<https://devfeed.tech/tags/performance.md>), [react](<https://devfeed.tech/tags/react.md>), [request](<https://devfeed.tech/tags/request.md>), [scale](<https://devfeed.tech/tags/scale.md>), [server](<https://devfeed.tech/tags/server.md>), [services](<https://devfeed.tech/tags/services.md>)

## AI overview

This tutorial explains batching client operations in GraphQL applications, especially with Apollo Client. It covers how batching combines requests within a timing threshold, the tradeoffs of batching, and why sending an array of operations can preserve per-operation metrics while reducing network round trips.

## Source excerpt

Modern apps are chatty--they require a lot of data, and thus make a lot of requests to underlying services to fulfill those needs. Layering GraphQL over your services solves this issue, since it encapsulates multiple requests into a single operation, avoiding the cost of multiple round trips. While GraphQL encourages this style of data fetching, React encourages developers to split up data fetching logic to be colocated with the components that use it.