2019-12-18
1836
#graphql#react
Ebenezer Don
11317
Dec 18, 2019 â‹… 6 min read

GraphQL + React for noobs

Ebenezer Don Full-stack software engineer with a passion for building meaningful products that ease the lives of users.

Recent posts:

10 Node.js 24 features you're probably not using

10 Node.js 24 features you’re probably not using

The Node.js 24 release included significant updates. Explore 10 features you might not be using yet — but absolutely should be.

Emmanuel John
May 22, 2025 â‹… 8 min read
six CSS animation libraries to bring your project to life in 2025

6 CSS animation libraries to bring your project to life in 2025

Explore six of the best, easiest, most configurable, and convenient CSS animation libraries available in 2025.

Murat YĂĽksel
May 22, 2025 â‹… 8 min read
Understanding Next.js Middleware Vulnerability

Understanding Next.js’s middleware vulnerability

A critical auth bypass vulnerability in Next.js lets attackers skip middleware checks by faking the x-middleware-subrequest header.

David Omotayo
May 21, 2025 â‹… 6 min read
How To Build A Secure File Upload System In Astro

How to build a secure file upload system in Astro

Build a secure file upload system using Astro’s server-side rendering, Cloudinary’s SDKs, and native integration.

Emmanuel John
May 21, 2025 â‹… 19 min read
View all posts

2 Replies to "GraphQL + React for noobs"

  1. Thanks for this article, Ebenezer. In recent months I’ve been using axios to make traditional API calls. Now, on a personal project of my own, I’m going to try using GraphQL. Sounds like you’re a proponent of using the Apollo Client? Quick question: With Apollo installed, what do you use for non-local state management? I’ve read that Apollo can be used as as substitute for the Context API and Redux. My recent experience has been with the Context API. I wonder if it makes sense to have an app with both Apollo and the Context API?

  2. Hi Robert, I’m glad you found this helpful. I think to a great extent, choosing a state management tool boils down to personal choice.

    In this case, I think using the Apollo cache would be easier. You might want to check out this article on Managing Local State with Apollo Client and React Hooks: https://itnext.io/managing-local-state-with-apollo-client-and-react-hooks-9ad357e6d649

    I also have an article on React Hooks and the Context API where I tried making the UseContext setup as straightforward as I can: https://blog.logrocket.com/use-hooks-and-context-not-react-and-redux/

Leave a Reply