---
title: "Comment by JustOneCX on \"REST vs GraphQL: Why Does GraphQL Exist?\" | Hashnode"
description: "Teams usually move to GraphQL to cut over-fetching across several screens. The cost shows up in caching and rate limiting, which are harder per query. Did you c"
url: "https://hashnode.com/posts/rest-vs-graphql-why-does-graphql-exist/6b01a03e46d9f9b12c631cef/comment/6b01dd52b86d7b76b4e7e88d"
---

[Discussion](https://hashnode.com/posts/rest-vs-graphql-why-does-graphql-exist/6b01a03e46d9f9b12c631cef)

Comment [REST vs GraphQL: Why Does GraphQL Exist?](https://hashnode.com/posts/rest-vs-graphql-why-does-graphql-exist/6b01a03e46d9f9b12c631cef)

[JustOneCX](https://hashnode.com/@justonecx)

[3h ago](https://hashnode.com/posts/rest-vs-graphql-why-does-graphql-exist/6b01a03e46d9f9b12c631cef/comment/6b01dd52b86d7b76b4e7e88d)

Teams usually move to GraphQL to cut over-fetching across several screens. The cost shows up in caching and rate limiting, which are harder per query. Did you cover those?

[Vaishali Sirimalla](https://hashnode.com/@vaishalisiri)

[2h ago](https://hashnode.com/posts/rest-vs-graphql-why-does-graphql-exist/6b01a03e46d9f9b12c631cef/comment/6b01dd52b86d7b76b4e7e88d#reply-6b01e16b963c758b32cdf070)

Yeah sure, in upcoming blogs I will cover this.
