Apps for SharePoint have various options for storing application and configuration data, including the SharePoint app property bag, lists, document libraries, Windows Azure storage, and remote servers. The document discusses these options and provides guidance on best practices for data storage depending on the type of app and data. It recommends using remote servers or Windows Azure for sensitive or large amounts of data in provider-hosted apps, and SharePoint lists or libraries for large non-sensitive data in SharePoint-hosted apps.

1. APPS FOR SHAREPOINT
DATA STORAGE IN APPS
STORE YOUR APP AND CONFIGURATION DATA USING ANY OF THE VARIOUS STORAGE OPTIONS
What kind of data is it?
Where can it be stored?
Application
data
Data to and from app
Remote
server
Configuration
data
App configuration settings
and connection strings
Remote
server
SharePoint list and
Document library
SharePoint list and
Document library
Windows
Azure
App property
bag
Windows
Azure
DATA STORAGE OPTIONS
App
property bag
Windows Azure
SQL Database
Windows Azure
Drive/Blobs
Windows Azure
Tables
▪ Lightweight and easy to use
▪ Useful for structured data
▪ Relational database capabilities
- relational database service
extends core SQL Server capabilities to the cloud
▪ Data integrity can be maintained
▪ Suitable for unstructured data /
large data
▪ Add all certifications of Azure
tables in blobs as well
▪ Fault-tolerant, ISO 27001
certified NoSQL key-value
store; useful
for apps that store large
amounts of non-relational data
▪ No standard user interface
available
▪ Requires a middle layer
▪ Does not support large
amount of data; data larger
than maximum supported by
Windows Azure SQL database
Provider-hosted 
SharePoint-hosted 
Provider-hosted 
SharePoint-hosted 
▪ No server-side code for
SharePoint-hosted apps; only
client-side JavaScript
▪ Provisions an isolated sub-web
on a parent web
Provider-hosted 
SharePoint-hosted 
Provider-hosted 
SharePoint-hosted 
SharePoint
List
SharePoint
Doc Library
Windows Azure
Queues
Remote
Servers
▪ Create a backlog of work to
process synchronously and
pass messages from a Windows
Azure web role to a Windows
Azure worker role
▪ Independent; developers have
full control; bring your own
hosting server infrastructure
▪ Supports workflows and
remote event receivers; uses
standard UI; apply different
permissions to lists
▪ Supports large amounts of
data and provides advantages
of SharePoint lists; can easily
add binary data
▪ No server-side code allowed
for SharePoint-hosted apps;
only client-side JavaScript
▪ Provisions an isolated sub-web
on a parent web
▪ Developers will need to isolate
tenants
▪ Not recommended for app
data storage
▪ No transaction handling; not
recommended for complex
data relationships and large
amounts of data
▪ No transaction handling;
not recommended for
complex data relationships
Provider-hosted 
SharePoint-hosted 
Provider-hosted 
SharePoint-hosted 
Provider-hosted 
SharePoint-hosted 
Provider-hosted 
SharePoint-hosted 
BEST PRACTICES FOR DATA STORAGE
Provider-hosted
Storage for
Sensitive Data
Storage for
Large Data
http://dev.office.com
SharePoint-hosted
Can store and run the encryption on any remote server
Not recommended
Remote server database
SharePoint doc library or SharePoint asset library
© 2014 Microsoft. All rights reserved.