A Deep Dive into Strapi GraphQL

REST API design pattern is one of the best practices when building API’s for the back end of any application. It’s benefits supersede it’s downside. When fetching data from an extensive REST application with many database relationships, there is can be an information overload problem.

This is a companion discussion topic for the original entry at https://strapi.io/blog/a-deep-dive-into-strapi-graph-ql

Is this guide written for Strapi V4? If not, how much is still valid for V4?

This article is being updated for v4 and will be published soon, will let you know when it is live.

Graphql in Strapi is very slow. Several times slower for the same query in Rest if you have relations. Not apt for production applications. Is there any plans to improve the performance?