---
title: "Discussion on \" REST vs GraphQL: A Practical Comparison\n\" | Hashnode"
description: "Discussion on \" REST vs GraphQL: A Practical Comparison\n\". GraphQL doesn't make REST obsolete — it solves a specific problem REST has, and creates a couple of its own. Here's the honest tradeoff."
url: "https://hashnode.com/posts/rest-vs-graphql-a-practical-comparison/6a9aaeec2dfefc9531a51124"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [REST vs GraphQL: A Practical Comparison](https://jayesh-sojitra.hashnode.dev/rest-vs-graphql-a-practical-comparison?utm_source=hashnode&utm_medium=feed)

GraphQL doesn't make REST obsolete — it solves a specific problem REST has, and creates a couple of its own. Here's the honest tradeoff.

Sep 4 · 3 min read · jayesh-sojitra.hashnode.dev  
Read the article

-   [#graphql](https://hashnode.com/tag/graphql)
-   [#rest](https://hashnode.com/tag/rest)
-   [#webdevelopment](https://hashnode.com/tag/webdevelopment)
-   [#frontend-development](https://hashnode.com/tag/frontend-development)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#apidesign](https://hashnode.com/tag/apidesign)
-   [#techtips](https://hashnode.com/tag/techtips)

## Written by

[Jayesh Sojitra](https://hashnode.com/@jayeshsojitra)

@jayeshsojitra

  
[View profile](https://hashnode.com/@jayeshsojitra)

Jayesh Sojitra | AI & Frontend

## Responses

Markdown supported · ⌘↵ to post

No responses yet.