There are a lot of different options when it comes to communicating with SharePoint. Here’s some advice when to use them when building Apps:
- Apps that offer Create/Read/Update/Delete (CRUD) actions against SharePoint or BCS external data, and are hosted on an application server separated by a firewall benefit most from using the JavaScript client object model.
- Server-side code in Apps that offer Create/Read/Update/Delete (CRUD) actions against SharePoint or BCS external data, and are hosted on an application server but not separated by a firewall mainly benefit from using the .managed client object model, but the Silverlight client object model, JavaScript client object model or REST are also options.
- Apps hosted on non-Microsoft technology (such as members of the LAMP stack) will need to use REST.
- Windows phone apps need to use the mobile client object model.
- If an App contains a Silverlight application, it should use the Silverlight client object model.
- Office Apps that also work with SharePoint need to use the JavaScript client object model.
See http://msdn.microsoft.com/en-us/library/jj164060(v=office.15).aspx 
for more general guidelines concerning client API choices and solution development.
Keep track of newer insights at TechNet Wiki page http://social.technet.microsoft.com/wiki/contents/articles/13637.sharepoint-2013-best-practices-what-client-api-should-you-choose-when-building-apps.aspx
Like this:
Like Loading...
