Apps for SharePoint can be categorized in at least four important ways:
- Where the components of the app are stored. The possibilities are:
- Externally:Remote components are persisted in databases, servers, or cloud-based services, that are external to the SharePoint farm.
- In SharePoint: SharePoint components, such as list templates, modules, workflows, site pages, Web Parts, and custom content types, are persisted within the SharePoint content database.
- Mixed: An app can include both SharePoint and external components.
- Whose hardware, or cloud service account, hosts the remote components. The possibilities are:
- The developer's hardware or cloud account: The components are hosted on the developer's hardware or cloud service account.
- The customer's hardware, private cloud, or Windows Azure Web Sites account: The components are hosted in a Windows Azure Web Sites account that is associated with a customer's SharePoint Online account, or in a private Windows Azure Web Sites cluster associated with the customer's SharePoint farm.
- Whose logic controls the deployment of the components. The possibilities are:
- Custom logic of the developer: When the developer is hosting the components of the app, the developer provides the deployment logic.
- SharePoint installation logic: SharePoint components are deployed to host webs and app webs by SharePoint when a customer installs the app.
- Autohosting logic: SQL Server databases and ASP.NET web applications can be deployed automatically to a Windows Azure Web Site in SharePoint Online, by using the SharePoint autohosting system. Developers need only include the appropriate Web Deploy packages and DACPACs in the app package and reference them in the app manifest.
- Where the host website on which the app is to be installed is located. The possibilities are:
- On premises behind a firewall
- On premises without a firewall
- In SharePoint Online
No comments:
Post a Comment