# GraphQL & Caching: The Elephant in the Room

DevFeed: [GraphQL & Caching: The Elephant in the Room](<https://devfeed.tech/articles/graphql-caching-the-elephant-in-the-room-23326.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/graphql-caching-the-elephant-in-the-room>)

Author: Marc-André Giroux

Published: 2019-06-25T22:43:06Z

Content type: article

Language: en

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

Topics: [GraphQL](<https://devfeed.tech/topics/graphql.md>), [Caching](<https://devfeed.tech/topics/caching.md>), [HTTP](<https://devfeed.tech/topics/http.md>), [client](<https://devfeed.tech/topics/client.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cache](<https://devfeed.tech/tags/cache.md>), [caching](<https://devfeed.tech/tags/caching.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [http](<https://devfeed.tech/tags/http.md>)

## AI overview

This article examines caching in GraphQL and explains why the claim that GraphQL breaks caching lacks nuance. It distinguishes client-side, server-side, application-level, and HTTP caching, noting that GraphQL can support server and client caching while offering less use of HTTP semantics by default than styles such as REST.

## Source excerpt

This post is a preview of my upcoming book on GraphQL. It is an introduction to a caching & performance chapter, taking a look at the whole caching & GraphQL situation to remove confusion and show a more nuanced way of looking at it. If you're interested in learning more about the book, I would really appreciate if you signed up for the newsletter.