The name "apps for SharePoint" is changing to "SharePoint Add-ins".
During the transition, the documentation and the UI of some SharePoint
products and Visual Studio tools might still use the term "apps for
SharePoint".
SharePoint Add-ins widen the range of possible programming languages and technology stacks that you can use when you work with SharePoint resources and services. The precise range of options depends on both the type of add-in and the hosting pattern that you choose. It’s also possible to mix patterns.
The following image can give you an overview of the entire app schema:
SharePoint hosted app / add-ins
Provider hosted apps / add-ins
Provider-hosted apps for SharePoint include components that are deployed and hosted outside the SharePoint farm. They are installed to the host web, but their remote components are hosted on another server. Figure 2 illustrates the basic architecture of a provider-hosted app.
Auto-hosted apps / add-ins
Auto-hosted apps for SharePoint are cloud-hosted apps whose remote components are provisioned and deployed for you on Windows Azure. As with a provider-hosted app, an auto-hosted app for SharePoint can interact with a SharePoint website but also uses resources and services that are located on a remote site that is hosted by Windows Azure. The SharePoint 2013 installation provisions and deploys these resources for you.
SharePoint Add-ins widen the range of possible programming languages and technology stacks that you can use when you work with SharePoint resources and services. The precise range of options depends on both the type of add-in and the hosting pattern that you choose. It’s also possible to mix patterns.
The following image can give you an overview of the entire app schema:
SharePoint hosted app / add-ins
SharePoint-hosted apps, or apps where all components are hosted on either an on-premises or Office 365 SharePoint farm. SharePoint-hosted apps are installed on a SharePoint 2013 website, called the host web. They have their resources hosted on an isolated sub site of a host web, called the app web. It’s important to know the difference between host webs and app webs. Figure 1 illustrates the basic architecture of a SharePoint-hosted app.
Provider hosted apps / add-ins
Provider-hosted apps for SharePoint include components that are deployed and hosted outside the SharePoint farm. They are installed to the host web, but their remote components are hosted on another server. Figure 2 illustrates the basic architecture of a provider-hosted app.
Auto-hosted apps / add-ins
Auto-hosted apps for SharePoint are cloud-hosted apps whose remote components are provisioned and deployed for you on Windows Azure. As with a provider-hosted app, an auto-hosted app for SharePoint can interact with a SharePoint website but also uses resources and services that are located on a remote site that is hosted by Windows Azure. The SharePoint 2013 installation provisions and deploys these resources for you.
No comments:
Post a Comment