--- title: GraphQL vs REST APIs -- The Case Against GraphQL | daily.dev description: GraphQL offers efficient data retrieval, flexibility in queries, reduced number of requests, versioning and backward compatibility, and real-time data with... canonical: https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GraphQL vs REST APIs -- The Case Against GraphQL | daily.dev og:description: GraphQL offers efficient data retrieval, flexibility in queries, reduced number of requests, versioning and backward compatibility, and real-time data with... og:url: https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo og:image: https://api.daily.dev/og/posts/ux0eqonWO.png og:image:alt: GraphQL vs REST APIs -- The Case Against 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. # GraphQL vs REST APIs -- The Case Against GraphQL **[asayer](https://daily.dev/sources/asayer)** · 14 min read · 17 upvotes · 0 comments ## Summary GraphQL offers efficient data retrieval, flexibility in queries, reduced number of requests, versioning and backward compatibility, and real-time data with subscriptions. However, it also has challenges in implementation, performance, caching, and security. REST APIs remain preferable in scenarios involving simplicity, statelessness, caching, limited bandwidth, and a mature ecosystem. Transitioning to GraphQL requires consideration of the learning curve, schema design and migration, updating client-side implementations, backend adjustments and resolvers, and performance considerations. The decision depends on factors such as data complexity, scalability requirements, team expertise, data fetching efficiency, project scope and complexity, tooling and ecosystem support, and long-term maintainability. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments --- Tags: [#backend](https://daily.dev/tags/backend), [#data-retrieval](https://daily.dev/tags/data-retrieval), [#graphql](https://daily.dev/tags/graphql), [#rest-api](https://daily.dev/tags/rest-api) [View this post on daily.dev](https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo) ```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":"GraphQL vs REST APIs -- The Case Against GraphQL","url":"https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo"},"datePublished":"2024-03-26T08:53:55.580Z","dateModified":"2025-09-06T02:42:48.332Z","description":"GraphQL offers efficient data retrieval, flexibility in queries, reduced number of requests, versioning and backward compatibility, and real-time data with...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4b3a33d1c001649ea3bc7cd1cb4a81c9?_a=AQAEufR","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/4b3a33d1c001649ea3bc7cd1cb4a81c9?_a=AQAEufR","isAccessibleForFree":true,"articleSection":"asayer","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":"asayer","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/be8d9d38650943c8a1718ba79f23e9ac","url":"https://daily.dev/sources/asayer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/graphql-vs-rest-apis----the-case-against-graphql-ux0eqonwo","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":17},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"backend,data-retrieval,graphql,rest-api","timeRequired":"PT14M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"asayer","item":"https://daily.dev/sources/asayer"},{"@type":"ListItem","position":3,"name":"GraphQL vs REST APIs -- The Case Against GraphQL"}]} ```