SharePoint Add-in Recipe - Performance Considerations

Todd Baginski

by Todd Baginski on 7/21/2015

Share this:

Article Details

Date Revised:

Applies to:
csom, Development, Office 365, Office 365 Patterns and Practices Guidance, OfficeDev, patterns and practices, performance, PnP guidance, SharePoint 2013, SharePoint REST API


The approaches you take to ensure optimal performance with SharePoint is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario most code operations took place in the SharePoint Server-side Object Model code.

In an SharePoint Add-in model scenario, the SharePoint Client-side Object Model (CSOM) and/or the SharePoint REST API are used to execute code.

The major difference between the two models is server-side code versus client-side code. In the SharePoint Add-in model, because code is executed via clients, additional network traffic occurs. Minimizing the number of API call round trips to the SharePoint server will increase the performance of your SharePoint Add-ins and reduce the amount of resources consumed by your SharePoint site.

Additionally, in the SharePoint Add-in model, because code is executed via clients there could be long delays before a response is received. Caching data for long running operations (like the User Profile APIs) can reduce the amount of time it takes to return information or receive confirmation a process is complete.

You can read the rest of this Office 365 Patterns and Practices Guidance article on GitHub, here:

Topic: Development

Sign in with

Or register