With the deprecation of the REST API product and variant endpoints will there be an adjustment to the graphql query costs/limits for the Product graphql queries? Considering I can currently get multliple Products (up to 250) with all of its properties and all of its variants in a single REST API request migrating to graphql for certain tasks is incredibly inefficient and expensive. Where one HTTP request was needed several hundred will be required to migrate code without having to also migrate to use Bulk operation queries and the associated webhook to wait for the callback.
We have now raised the rate limits for standard shops from 50points/second to 100 points / second. We have also updated the query calculations for querying connections. With these changes, your app should be able to maintain the same or higher throughput as before when using REST.
To learn more about how to optimize your app for throughput, read more here
To learn more about querying product data in GraphQL read here
Thanks for the reply and for the information regarding the increased points/second, Though I remain skeptical that it would be possible to get 250 products with all their attributes and variants in the same amount of time or better using graphql. I’d be very interested in seeing the data to back that claim
Another example is “products/count.json”. With REST I get a number back. simple and works great - it has for the last 10+ years. With GraphQL getting the count of products is not possible.
Now have to make many calls walking the products with pagination and keeping count of the iterations.
