So… what changes should we expect to see here?
If Atlassian built Connect Apps they’d experience the pain of having absolutely no idea how rate limiting actually works in practice, despite your helpful write up.
While I understand there are 4 cost budgets now, I have no idea how those cost budgets compare to each other, or to REST API behaviour from 6 or 12 months ago.
Additionally I’m not allow to run performance tests to figure any of this out according to the docs you link to, and anecdotally I know that rate limiting behaves differently on different Jira instances based off experience back before vendors were told not to run performance tests. Unless that has changed? I can’t run performance tests to find out…
While I really appreciated that you’re trying to provide useful information for vendors, its really hard to build a performant service that does not violate rate limits based on the information that has been provided.
If customers complain about performance being slow we have no idea whether we can increase concurrency safely. If customers complain about feature failures we have no way to establish how much we need to reduce the concurrency or frequency of requests, unless we “do it live” with production traffic.
Apologies for the rant. I appreciate this is a non-trivial problem to solve and that Atlassian have other priorities, I’d just really like to hear that it is a problem that is actually being worked on because its really painful for vendors.