Regarding GraphQL vs REST I think you realized your reasons for the migration weren't solid enough. Maybe you can call the GraphQL only for those endpoints where you are having performance issues and see if you get a speed up. I'm not familiar with Shopify's API though.
Regarding cursors based pagination: Slack's API has cursor based pagination, so has a framework like Django REST.
I think here you inverted the two technologies:
From my findings and based on some others' reviews, I was skeptical about migrating from GraphQL to REST
Hi Hatem!
Regarding GraphQL vs REST I think you realized your reasons for the migration weren't solid enough. Maybe you can call the GraphQL only for those endpoints where you are having performance issues and see if you get a speed up. I'm not familiar with Shopify's API though.
Regarding cursors based pagination: Slack's API has cursor based pagination, so has a framework like Django REST.
I think here you inverted the two technologies:
Hi Rhymes!
As I’ve mentioned, mixing both APIs will only add complexity to the code base which can be confusing for the rest of the team.
Thank you very much for pointing out Slack’s and Danjgo’s, very helpful 🙌🏼
You’re right, I made a little switcheroo over there. Thank you, it’s fixed now.