Why should we need an App deployment model
To fully understand Microsoft's motivation for beginning to transition away from SharePoint solution to the new app model you must first understand the challenges in SharePoint solution..
Custom developed SharePoint solution runs within the host environment like Sandbox Solution runs within the sandbox worker process. This behavior is not so good for farm's stability.
Second, SharePoint developed solutions with complex logic and highly dependability are not so easy to upgrade. What if any custom code is depended on a feature and that feature is deprecated or not coming in next version ?
Third is security and permission, code runs under the permission of a specific user. Which could be risky sometimes.
So, App models solve these challenges..ex.
1.It is light weight. It doesn't carry extra markup like a webPart.
2. It runs in isolation of SharePoint. It has to authentication separately before using.
3. Use any language - like HTML, JavaScript, PHP, or .NET - and your favorite web development tools - like Visual Studio 2012 or the new "Napa" Office 365 Development Tools.
4. Easy to upgrade.
To fully understand Microsoft's motivation for beginning to transition away from SharePoint solution to the new app model you must first understand the challenges in SharePoint solution..
Custom developed SharePoint solution runs within the host environment like Sandbox Solution runs within the sandbox worker process. This behavior is not so good for farm's stability.
Second, SharePoint developed solutions with complex logic and highly dependability are not so easy to upgrade. What if any custom code is depended on a feature and that feature is deprecated or not coming in next version ?
Third is security and permission, code runs under the permission of a specific user. Which could be risky sometimes.
So, App models solve these challenges..ex.
1.It is light weight. It doesn't carry extra markup like a webPart.
2. It runs in isolation of SharePoint. It has to authentication separately before using.
3. Use any language - like HTML, JavaScript, PHP, or .NET - and your favorite web development tools - like Visual Studio 2012 or the new "Napa" Office 365 Development Tools.
4. Easy to upgrade.
