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:

A Guide To Wrapper Vs. Container Classes In CSS

A guide to wrapper vs. container classes in CSS

A breakdown of the wrapper and container CSS classes, how they’re used in real-world code, and when it makes sense to use one over the other.

Temitope Oyedele
Jul 7, 2025 ⋅ 10 min read
Stagehand and Gemini logos on a gradient background symbolizing AI web automation

How to build a web-based AI agent with Stagehand and Gemini

This guide walks you through creating a web UI for an AI agent that browses, clicks, and extracts info from websites powered by Stagehand and Gemini.

Elijah Asaolu
Jul 4, 2025 ⋅ 8 min read
Getting Started With Claude 4 API: A Developer's Walkthrough

Getting started with Claude 4 API: A developer’s walkthrough

This guide explores how to use Anthropic’s Claude 4 models, including Opus 4 and Sonnet 4, to build AI-powered applications.

Andrew Baisden
Jul 3, 2025 ⋅ 16 min read
ai dev tool power rankings

AI dev tool power rankings & comparison [July 2025 edition]

Which AI frontend dev tool reigns supreme in July 2025? Check out our power rankings and use our interactive comparison tool to find out.

Chizaram Ken
Jul 2, 2025 ⋅ 3 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