{"id":4960,"date":"2026-04-01T15:19:49","date_gmt":"2026-04-01T07:19:49","guid":{"rendered":"https:\/\/trg.unhas.ac.id\/datascienceai\/?p=4960"},"modified":"2026-04-09T20:37:52","modified_gmt":"2026-04-09T12:37:52","slug":"rest-vs-graphql-which-api-truly-performs-better-in-real-world-systems","status":"publish","type":"post","link":"https:\/\/trg.unhas.ac.id\/datascienceai\/rest-vs-graphql-which-api-truly-performs-better-in-real-world-systems\/","title":{"rendered":"REST vs GraphQL: Which API Truly Performs Better in Real-World Systems?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>MAKASSAR, Indonesia \u2013 <em>Apr 1 2026<\/em>\/DSAI\/<\/em> \u2014 In today\u2019s data-driven world, modern applications rely heavily on Application Programming Interfaces (APIs) to connect systems, deliver data, and power digital services. But developers often face a critical decision: should they stick with the traditional <strong>REST API<\/strong>, or adopt the newer, flexible <strong>GraphQL<\/strong>? A recent study provides real-world insights into this debate, revealing that the answer is not as simple as choosing one over the other.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The research, published in the journal <em>Computers<\/em>, evaluates the performance of REST and GraphQL APIs within a <strong>large-scale, real operational system<\/strong>\u2014not simulations, but actual live transactions from a university information system. This makes the findings especially valuable for developers working with real-world applications .<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img fetchpriority=\"high\" decoding=\"async\" width=\"915\" height=\"815\" src=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-10.png\" alt=\"\" class=\"wp-image-4961\" srcset=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-10.png 915w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-10-300x267.png 300w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-10-768x684.png 768w\" sizes=\"(max-width: 915px) 100vw, 915px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Unlike many previous studies, this research introduces a <strong>novel evaluation method<\/strong>. It runs REST and GraphQL in parallel environments, ensuring fair comparison by distributing identical user requests to both systems simultaneously. The system measures four key performance indicators: <strong>response time, throughput, CPU load, and memory usage<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-large\"><img decoding=\"async\" width=\"1024\" height=\"622\" src=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-1024x622.png\" alt=\"\" class=\"wp-image-4963\" srcset=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-1024x622.png 1024w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-300x182.png 300w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-768x467.png 768w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png 1048w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The results reveal a fascinating trade-off. REST clearly dominates in speed. According to the <em>results table on page 9<\/em>, REST achieves an average response time of <strong>922.85 ms<\/strong>, nearly twice as fast as GraphQL\u2019s <strong>1864.50 ms<\/strong> . It also handles more requests per second, with higher throughput performance (<em>page 10<\/em>).<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img decoding=\"async\" width=\"750\" height=\"863\" src=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-11.png\" alt=\"\" class=\"wp-image-4962\" srcset=\"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-11.png 750w, https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-11-261x300.png 261w\" sizes=\"(max-width: 750px) 100vw, 750px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">However, GraphQL shines in a different area\u2014<strong>efficiency<\/strong>. The study shows that GraphQL uses significantly less system resources. On average, it consumes around <strong>47% CPU<\/strong>, compared to REST\u2019s <strong>75%<\/strong>, and uses much less memory (<strong>~41 MB vs ~69 MB<\/strong>) . This means GraphQL is more suitable for systems where resource optimization is critical.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Why does this happen? The answer lies in their architecture. REST uses multiple endpoints, allowing faster access but requiring more system resources. GraphQL, on the other hand, uses a <strong>single endpoint with customizable queries<\/strong>, reducing unnecessary data transfer but increasing processing complexity .<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This research strongly supports several <strong>Sustainable Development Goals (SDGs)<\/strong>. It contributes to <strong>SDG 9: Industry, Innovation, and Infrastructure<\/strong> by advancing efficient digital system design. It also aligns with <strong>SDG 8: Decent Work and Economic Growth<\/strong>, as better-performing systems improve productivity and scalability in businesses. Additionally, it supports <strong>SDG 17: Partnerships for the Goals<\/strong>, reflecting international collaboration across institutions in Indonesia and Japan.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ultimately, the study delivers a clear message: there is no \u201cone-size-fits-all\u201d solution. If your system prioritizes <strong>speed and high-frequency requests<\/strong>, REST remains the better choice. But if your focus is on <strong>flexibility and resource efficiency<\/strong>, GraphQL offers significant advantages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Article Metadata (Source of This Popular Scientific Writing):<\/strong><br>Title: <em>Evaluating GraphQL and REST API Services Performance in a Massive and Intensive Accessible Information System<\/em><br>Journal: <em>Computers<\/em><br>Publisher: MDPI<br>Publication Date: 27 October 2021 (Volume 10, Article 138)<br>DOI: <a href=\"https:\/\/doi.org\/10.3390\/computers10110138\">https:\/\/doi.org\/10.3390\/computers10110138<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Authors &amp; Contact:<\/strong><br>Armin Lawi*, Benny L. E. Panggabean, Takaichi Yoshida<br>Hasanuddin University (Indonesia), Pancasakti University (Indonesia), Kyushu Institute of Technology (Japan)<br>E-mail: <a href=\"mailto:armin@unhas.ac.id\">armin@unhas.ac.id<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the end, the future of API design is not about replacing REST with GraphQL\u2014but about knowing <strong>when to use each one intelligently<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>MAKASSAR, Indonesia \u2013 Apr 1 2026\/DSAI\/ \u2014 In today\u2019s data-driven world, modern applications rely heavily on Application Programming Interfaces (APIs) to connect systems, deliver data, and power digital services. But developers often face a critical decision: should they stick with the traditional REST API, or adopt the newer, flexible GraphQL? A recent study provides real-world [&hellip;]<\/p>\n","protected":false},"author":60,"featured_media":4963,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_uag_custom_page_level_css":"","_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[1],"tags":[46,37,38],"class_list":["post-4960","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-sdg17","tag-sdg8","tag-sdg9"],"acf":[],"uagb_featured_image_src":{"full":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"thumbnail":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-150x150.png",150,150,true],"medium":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-300x182.png",300,182,true],"medium_large":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-768x467.png",768,467,true],"large":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-1024x622.png",1024,622,true],"1536x1536":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"2048x2048":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false]},"uagb_author_info":{"display_name":"Admin DSAI","author_link":"https:\/\/trg.unhas.ac.id\/datascienceai\/author\/admindatascienceai\/"},"uagb_comment_info":0,"uagb_excerpt":"MAKASSAR, Indonesia \u2013 Apr 1 2026\/DSAI\/ \u2014 In today\u2019s data-driven world, modern applications rely heavily on Application Programming Interfaces (APIs) to connect systems, deliver data, and power digital services. But developers often face a critical decision: should they stick with the traditional REST API, or adopt the newer, flexible GraphQL? A recent study provides real-world&hellip;","rttpg_featured_image_url":{"full":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"landscape":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"portraits":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"thumbnail":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-150x150.png",150,150,true],"medium":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-300x182.png",300,182,true],"large":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12-1024x622.png",1024,622,true],"1536x1536":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false],"2048x2048":["https:\/\/trg.unhas.ac.id\/datascienceai\/wp-content\/uploads\/sites\/76\/2026\/04\/image-12.png",1048,637,false]},"rttpg_author":{"display_name":"Admin DSAI","author_link":"https:\/\/trg.unhas.ac.id\/datascienceai\/author\/admindatascienceai\/"},"rttpg_comment":0,"rttpg_category":"<a href=\"https:\/\/trg.unhas.ac.id\/datascienceai\/category\/uncategorized\/\" rel=\"category tag\">Uncategorized<\/a>","rttpg_excerpt":"MAKASSAR, Indonesia \u2013 Apr 1 2026\/DSAI\/ \u2014 In today\u2019s data-driven world, modern applications rely heavily on Application Programming Interfaces (APIs) to connect systems, deliver data, and power digital services. But developers often face a critical decision: should they stick with the traditional REST API, or adopt the newer, flexible GraphQL? A recent study provides real-world&hellip;","_links":{"self":[{"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/posts\/4960","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/users\/60"}],"replies":[{"embeddable":true,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/comments?post=4960"}],"version-history":[{"count":2,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/posts\/4960\/revisions"}],"predecessor-version":[{"id":5149,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/posts\/4960\/revisions\/5149"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/media\/4963"}],"wp:attachment":[{"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/media?parent=4960"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/categories?post=4960"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trg.unhas.ac.id\/datascienceai\/wp-json\/wp\/v2\/tags?post=4960"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}