New throttling policy is in the planning stage: "Concurrent Requests Limit Policy"

[#1]

We're getting ready to introduce a new Throttling Policy for the Visma.net Financials API which is called "Concurrent Requests Limit Policy". The reason behind this methodology is to be able to maintain a more stable performance while the API continues to grow with solid optimizations.

Currently, we're planning to implement this policy with "LOG ONLY"  mode enabled.
Meaning, the transactions made by the Clients who are sending Parallel / Concurrent calls are not going to be throttled during this period. 

In this way, we'll be able to gather more information about Clients / API Transactions so that we can analyse the inquiry behaviour. This will give us the opportunity to determine the optimal plausible limits to ensure the best and stable performance that our infrastructure can sustain with.

Information about "Concurrent Requests Limit Policy"

This policy is for limiting the number of concurrent requests a client can have per company/tenant. This policy doesn’t use a time interval for the check: it counts the “running” requests (not completed) of the calling client (on the requested company/tenant) at the time the check is performed.

For logging purposes, "only_log" - if set to true the policy will not throttle the request, just log the number of running requests the client has on the invoked company.

Please feel free to share your thoughts with us here or via developersupport@visma.com.

Thanks.