--- title: GraphQL: From Excitement to Deception | daily.dev description: GraphQL is a trendy technology that solves specific problems related to data fetching and allows for better data querying and manipulation. However, it also... canonical: https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: GraphQL: From Excitement to Deception | daily.dev og:description: GraphQL is a trendy technology that solves specific problems related to data fetching and allows for better data querying and manipulation. However, it also... og:url: https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw og:image: https://api.daily.dev/og/posts/2QzOaBtCW.png og:image:alt: GraphQL: From Excitement to Deception 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: From Excitement to Deception **[Better Programming](https://daily.dev/sources/btrprog)** · 7 min read · 26 upvotes · 2 comments ## Summary GraphQL is a trendy technology that solves specific problems related to data fetching and allows for better data querying and manipulation. However, it also comes with challenges such as performance optimization, typing complexity, tooling support, and security concerns. The decision to adopt GraphQL should be based on careful consideration of business requirements and the maturity of the ecosystem. ## 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. **@sschneider\_pvs** · 6 upvotes > Sadly, there are a lot of technical flaws in this article. > > REST does not have an official spec at all so that is a strength of Graphql. > > Monitoring graphql and/or deprecated field is possible. You can even monitor every step of processing a graphql request from parsing to validation to executions. > > there can be other clients that are not web clients, other services for example that may need different data. > > if you call a service from a resolver and it can identify books of being a part of the query you would usually make a join over books and have a single query. > > You can also restrict query... **@garren** · 1 upvotes > I felt this article was pretty balanced. I've tried to use Graphql for numerous things. The API and schema feel ok but never as good as the hyper. ## 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: [#performance](https://daily.dev/tags/performance), [#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-from-excitement-to-deception-2qzoabtcw) ```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: From Excitement to Deception","url":"https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw"},"datePublished":"2023-03-29T12:25:06.961Z","dateModified":"2024-04-13T18:33:31.786Z","description":"GraphQL is a trendy technology that solves specific problems related to data fetching and allows for better data querying and manipulation. However, it also...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/329adcc95e4d173daf768051b8d1d6fe?_a=AQAEufR","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/329adcc95e4d173daf768051b8d1d6fe?_a=AQAEufR","isAccessibleForFree":true,"articleSection":"Better Programming","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":"Better Programming","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/d957a1c828884dbb9543ba3e0beb6bc7","url":"https://daily.dev/sources/btrprog"},"commentCount":2,"discussionUrl":"https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":26},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":2}],"keywords":"performance,graphql,rest-api","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Better Programming","item":"https://daily.dev/sources/btrprog"},{"@type":"ListItem","position":3,"name":"GraphQL: From Excitement to Deception"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/graphql-from-excitement-to-deception-2qzoabtcw","comment":[{"@type":"Comment","text":"Sadly, there are a lot of technical flaws in this article.\nREST does not have an official spec at all so that is a strength of Graphql.\nMonitoring graphql and/or deprecated field is possible. You can even monitor every step of processing a graphql request from parsing to validation to executions.\nthere can be other clients that are not web clients, other services for example that may need different data.\nif you call a service from a resolver and it can identify books of being a part of the query you would usually make a join over books and have a single query.\nYou can also restrict query depth and costs as a security measure.\nAlso, handling errors in production, you would probably mask them as a security measure too.\nAnd if you understand Graphql errors more like Either monads that guarantee a response of either err or data, that concept is not new I’d say.\n…","datePublished":"2023-03-29T13:32:52.568Z","url":"https://daily.dev/posts/2QzOaBtCW#c-xcWtOQ4it","author":{"@type":"Person","name":"Stefan Schneider","url":"https://daily.dev/sschneider_pvs","image":"https://avatars.githubusercontent.com/u/86342787?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":6}},{"@type":"Comment","text":"I felt this article was pretty balanced. I’ve tried to use Graphql for numerous things. The API and schema feel ok but never as good as the hyper.","datePublished":"2023-03-30T08:50:00.854Z","url":"https://daily.dev/posts/2QzOaBtCW#c-hnnv9Y4aG","author":{"@type":"Person","name":"Garren","url":"https://daily.dev/garren","image":"https://avatars.githubusercontent.com/u/179458?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} ```