As mentioned many times in this blog, it is very easy to use SharePoint for document management and to maintain a small list without writing a custom application. But it is a nightmare when it comes to customizing SharePoint and interacting with it from other applications from APIs. One of the challenges is the throttling behavior.
We should agree that it is a SaaS application and Microsoft cannot fulfill all our API requests. They should throttle for the below reasons
- In order to manage noisy neighbors give equal consideration to all the tenant
- Ensure the availability of the entire system
The problem is the throttling details are not clear from the documentation. None available if we ended up in a situation where we need to use user-based flow. Forget about using ROPC flow from a daemon application.
Below is a flow chart that is trying to make sense of when our application will get throttled by Microsoft.
Click on it to open as SVG to navigate to the links.
No comments:
Post a Comment