I'm considering using GraphQL primarily for data fetching and REST for POST requests and updates in my project. The main reasons are that GraphQL allows for fetching exactly the fields we need and reduces over-fetching, which would benefit complex UI queries. On the other hand, REST is simpler for some endpoints, especially for handling external API integrations since it requires less boilerplate for mutations. I believe that using both could help leverage the strengths of each technology. However, I'm concerned about the complexity of managing both in the codebase.
2 Answers
GraphQL theoretically helps reduce the number of endpoints you have to manage by allowing more flexible queries, but it doesn’t fix over-fetching as commonly believed. Instead, it can sometimes lead to more database calls since you might fetch too much data only to filter it later. For smaller projects, you might not need it—stick with what works for you!
Mixing REST and GraphQL can be tricky. If GraphQL solves any problem you see with REST, then maybe you should just stick with one or the other. Maintaining both might complicate things more than necessary. If you want to do both, I’d suggest being careful about how they interact—having a hybrid setup can lead to confusion down the road.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically