SharePoint 2013’s App Model is designed, in part, to insulate application servers from one of the most common sources of Tier II and II support calls — custom solutions. So SharePoint stakeholders preparing a business case for implementing SharePoint Server 2013 may want to include references to the new development model as a method of reducing operating costs for the platform.
Readers with an interest in researching this topic may want to read a blog post on MSDN authored by Ed Hild back in February, 2013. This post is titled A Perspective on SharePoint 2013’s App Model – Part 1.
As Hild notes in his post, with reference to the traditional SharePoint application development model prior to the release of SharePoint 2013, “[t]he problem comes when these SharePoint applications are deployed to production and are now the responsibility of IT to maintain. Focused on keeping the lights on, this group is change adverse. Any custom code deployed onto the SharePoint servers complicates things. Does it change the way they do backup and recovery? How well was the code written and will it bring down the farm? Does it change the capacity planning activities that were done for out-of-the-box functionality? For these reasons there is a struggle as to how to effectively support these types of applications that are built leveraging SharePoint.” (quoted from a blog post on MSDN authored by Ed Hild. I’ve provided a link to the entire post, above).
If your organization would like to piece together a realistic opinion on the SharePoint 2013 App model, and what it can, or cannot do for your SharePoint objectives, please contact us.
© Rehmani Consulting, Inc. & Ira Michael Blonder, 2014 All Rights Reserved