The Challenge I Faced In our recent project, we started with a traditional REST API...
The Challenge I Faced
In our recent project, we started with a traditional REST API backend. The application was growing rapidly, and we realized we needed to migrate to a more flexible GraphQL API to reduce over-fetching and under-fetching issues.
The problem?
Our components were tightly coupled with REST API calls. Changing to GraphQL meant touching every single component that fetched data.
Solution?
I Migrated Our API From REST to GraphQL. Here's What Nobody Warned Me About. We spent 3...
The Practical Differences When I started building APIs, REST was the default. Then GraphQL...
REST developers exploring GraphQL alternatives
You've been building REST APIs — one endpoint for users, another for posts, another for comments. The...
Lesson 1.1 - REST vs GraphQL Goal Understand the difference between REST and...
TL;DR The N+1 problem is a general data-access anti-pattern that can appear in REST,...
