Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
We are seriously considering using Dynamics CRM as our backend for a web-app built out of portal that is to be publicly deployed.
Is there a maximum number of simultaneous requests that can be made at one time?
If there is a limitation, can we increase it?
Hope this helps -
Link shared by Goutam has all the details and additional details are in related links.
I just wanted to highlight few key points related to your question.
Your question is related to Service Protection API Limits. The service protection is enforced based on the following 3 factors
By default maximum concurrent requests a user account can make to Dynamics CRM is 52, please see below.
If this limit is exceeded, error message highlighted in the screenshot will be returned.
The concurrent limit 52 is imposed by the CRM web server that serves the requests.Typically the request to CRM is handled by multiple web servers with load balancing in place. Lets assume 100 simultaneous requests are coming from your public website, and the load balancer has split these into 50, 50 and passed on to two web servers, the service protection limit may not kick in.
If your Portal code hits the limit, as long as you have error handling and re-try mechanism in place, the requests could still be executed in second or third attempt depending on how many re-try you plan to have.
You could consider local caching to reduce requests to CRM. If your web site could cache frequently accessed data locally as much as it can, this would massively reduce the number of concurrent requests that hit CRM and might also make your web site respond faster if its serving from cache rather than requesting data from CRM every time.
I also found the following para is relevant to your question from the link
Portal applications typically send requests from anonymous users through a single service principal account. Because the service protection API limits are based on a per user basis, portal applications can hit service protection API limits based on the amount of traffic the portal experiences. Like interactive client applications, it isn't expected that the service protection API limits errors should be displayed to the portal end user. It is expected that the UI should disable further requests and display a message that the server is busy. The message may include the time when the application can begin accepting new requests."
Hope this helps
Business Applications communities