--- title: Choosing Between REST and GraphQL | daily.dev description: The dominant architecture for APIs in modern app development is REST. While REST is widely known, it has some downsides including overfetching and... canonical: https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Choosing Between REST and GraphQL | daily.dev og:description: The dominant architecture for APIs in modern app development is REST. While REST is widely known, it has some downsides including overfetching and... og:url: https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg og:image: https://api.daily.dev/og/posts/ev1BljtWG.png og:image:alt: Choosing Between REST and GraphQL og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Choosing Between REST and GraphQL **[DZone](https://daily.dev/sources/dz)** · 6 min read · 14 upvotes · 2 comments ## Summary The dominant architecture for APIs in modern app development is REST. While REST is widely known, it has some downsides including overfetching and inefficiencies concerning nested data. GraphQL is a new type of API architecture that is designed to be more flexible and efficient than REST with features like declarative data fetching. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@kkurko** · 0 upvotes > Clear explanation of prof and cons of both REST and GraphQL **@wuderstef** · 0 upvotes > I love this article. Very detailed and well written. But what about using both? What if you could use both GraphQL and REST.... TOGETHER. WunderGraph is a popular OSS tool that allows you to have all the pro's you listed in your article without the cons. Would love to see what you think. --- Tags: [#graphql](https://daily.dev/tags/graphql) [View this post on daily.dev](https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Choosing Between REST and GraphQL","url":"https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg"},"datePublished":"2022-04-25T20:46:14.543Z","dateModified":"2022-04-25T20:46:14.543Z","description":"The dominant architecture for APIs in modern app development is REST. While REST is widely known, it has some downsides including overfetching and...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bbf21d508c4bcef6b931727305b823cf","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/bbf21d508c4bcef6b931727305b823cf","isAccessibleForFree":true,"articleSection":"DZone","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"DZone","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/dz","url":"https://daily.dev/sources/dz"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":14},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"graphql","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"DZone","item":"https://daily.dev/sources/dz"},{"@type":"ListItem","position":3,"name":"Choosing Between REST and GraphQL"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/choosing-between-rest-and-graphql-ev1bljtwg","comment":[{"@type":"Comment","text":"Clear explanation of prof and cons of both REST and GraphQL","datePublished":"2022-05-01T17:35:13.712Z","dateModified":"2022-05-01T17:35:36.051Z","url":"https://daily.dev/posts/ev1BljtWG#c-d9kZIuEBM","author":{"@type":"Person","name":"Kirill Kurko","url":"https://daily.dev/kkurko","image":"https://avatars.githubusercontent.com/u/58859242?v=4"}},{"@type":"Comment","text":"I love this article. Very detailed and well written. But what about using both? What if you could use both GraphQL and REST… TOGETHER. WunderGraph is a popular OSS tool that allows you to have all the pro’s you listed in your article without the cons. Would love to see what you think.","datePublished":"2022-07-31T21:04:13.757Z","url":"https://daily.dev/posts/ev1BljtWG#c-bZ6xhdWB-","author":{"@type":"Person","name":"Stefan","url":"https://daily.dev/wuderstef","image":"https://media.daily.dev/image/upload/f_auto/v1659301478/avatars/wplfRxVNLgwbgVOAR85g6"}}]} ```