I have now investigated the GraphQL API for this usecase and suffice to say, I am not a fan. That is not to say that GraphQL doesn’t have great use cases. I can see how it can be very useful. However, using it for loading data into a data warehouse is certainly not one of them. Just trying to get some basic information leads to exceeding query cost limits. Running pagination way down for shops, on the other hand, makes it exceedingly slow.
Further, there is no GraphQL object for transactions either - I can only get it via the orders. So now I have the choice between:
-
get orders via GraphQL, which I can’t, because I can’t really get all the information I need in one API call, or
-
get orders via GraphQL, which I can’t, because I can’t get transactions data without additional API calls on a per-order basis
I can see that a lot of custom logic and numerous API calls would work, but that’s breaking my project goal. One of my previous suggestions would really be helpful here.
Best,
Bijan