6/11/2023 0 Comments Boomi groovy script exampleThe platform architecture includes Azure APIM and Boomi hosted on Azure VMs, connecting to D365 using Oauth2 client credentials authentication method. This article presents a solution that we have implemented in Boomi to enable the load balancing of the application users that call the Dataverse API. Each of these calls will be using credentials of a single D365 application user for server-to-server authentication, and in such a situation the 52 limit can be easily reached. In the context of a mobile application, a single request can result in an orchestration of multiple backend calls to the Dataverse API. While the execution time limit will not be an issue for synchronous interactions, the limit of 52 concurrent requests per user will affect applications that need to support many real-time synchronous patterns – which will be the main focus of this article. From the list above, the number of requests can be addressed by utilising the request throttling features of an API gateway. In Azure API Management (APIM), several rate-limiting policies such as ‘rate-limit-by-key' and/or ‘quota-by-key' are available for use. The number of concurrent requests made by the user ![]() The combined execution time of all requests made by the userĢ0 minutes (1200 seconds) within the 5-minute sliding window The cumulative number of requests made by the user
0 Comments
Leave a Reply. |