I opened a ticket and was told to ask here. The title is all I'm really asking but here's some additional context, there are multiple limitations listed around Platform API calls, concurrent/total/other, and to try and set better development standards we were going to start making everyone update their code base to use functions where we were previously using data actions.
For example: We currently call a data action to get estimated wait time, however there is also a function "GetQueueEstimatedWaitTime()" that is built into architect. Could we save on making a platform api call by using the function instead of calling a data action? Or does the function, indirectly call the Data Action?
As a general practice, we encourage everyone to use native Architect functions instead of data actions when possible. The Architect functions have been optimized in their design and do not count against your public API rate limits. When you use data actions to call a public API you are just using a straight-up OAUTH2 client credential grant and this will run you into rate limits, etc....
That's not to say that calling an Architect function couldn't run into a rate limit, it's just that the Architect team has put a lot of engineering effort into these native calls to make them as performant as possible in the context that they are being used. The data action/public API calls have to cater to a much wider series of use cases and can thus have to take a much more defensive posture in terms of rate limits, etc....
Thanks,
John Carnell
Director, Developer Engagement