2019-06-26
2020
#graphql
Sean Smith
3263
Jun 26, 2019 ⋅ 7 min read

GraphQL vs. REST: What you didn’t know

Sean Smith Software engineer.

Recent posts:

Using tsup To Bundle Your TypeScript Package

Using tsup to bundle your TypeScript package

Learn how to efficiently bundle your TypeScript package with tsup. This guide covers setup, custom output extensions, and best practices for optimized, production-ready builds.

Muhammad Ali
Feb 20, 2025 ⋅ 7 min read
Building A Telegram Bot With GrammY

Building a Telegram bot with grammY

Build a Telegram bot with Node.js and grammY to automate text, audio, and image responses using the Telegram API and Google Gemini.

Amazing Enyichi Agu
Feb 20, 2025 ⋅ 7 min read
Styling with the CSS box-shadow Property

Styling with the CSS box-shadow property

Use the `box-shadow` CSS property to create layered, neon, and neumorphic shadows in this detailed tutorial.

Oscar Jite-Orimiono
Feb 19, 2025 ⋅ 9 min read
Using Typescript Enums In React Native Web

A complete guide to TypeScript enums in React Native

Learn everything you need to know about how to use React Context — a great feature that enables you to manage and share state across the React application.

Kayode Adeniyi
Feb 19, 2025 ⋅ 8 min read
View all posts

4 Replies to "GraphQL vs. REST: What you didn’t know"

  1. As you said, I see the pros and cons on both, but as you also mentioned, both have advantages and some cool behaviors.

    I prefer trust on REST APIs for operations such as create/post, update/put and delete/delete.
    But the approach taken for retrieving different sections/resources at once given by GraphQL is nice and it is something that I missed sometime while coding richer on BE/FE applications following strictly REST APIs…

    So… Once it is possible to limit timeouts and max depth queries via GraphQL (https://www.howtographql.com/advanced/4-security/) I think it worth try have balance usage on both approach, and even mix others, like QueryDSL for Java…

    Just to conclude, I have to agree totally that when mixing different approaches sometimes looks a messy and not attractive… Specially if developers look at you traditional REST API and suddenly reaches a resources which is retrieved via GraphQL, looks a bit odd/weird, not to say a Frankstein.

Leave a Reply