SharePoint 2013 – Apps Vs Farm solutions

SharePoint 2013 has introduces the new Cloud App Model that enables you to create apps.
In SharePoint 2010 you had an Option to Add custom components to SharePoint via SharePoint Sandboxed or Farm solutions.But in SharePoint 2013 sandboxed solutions are deprecated.So all we got is the New App model and the Old SharePoint Farm solutions.
SharePoint 2013 – Apps Vs Farm solutions
To begin developing on SharePoint 2013 you need to first know what would you choose an App or farm solution? Here is a little Comparison chart –

Apps	Farm Solutions
What are apps - An app for SharePoint is a small, easy-to-use, stand-alone app that solves a specific end-user or business need.	What are Farm solutions - Farm solutions are pieces of functionality that extend the capabilities of a SharePoint website. They are Installed to the solution store of a farm by a farm administrator.
where does it run – The code for an app runs in different places, depending on where your app is hosted.They never run in the context of SharePoint Server, but they will run in the context of the browser or in the context of the hosted platform. SharePoint-hosted apps Provider-hosted and autohosted apps – In the cloud Apps that have a mix of components in SharePoint and in the cloud	where does it run – They are Installed to the solution store of a farm by a farm administrator. They run from the sharepoint server.
How Does It run - When you deploy a SharePoint-hosted app, SharePoint creates a new website called the app web. You can think of it as a dynamically created safe space for your app. Besides allowing you to store pages, lists, and libraries, the app web is also an isolated endpoint that your app can securely call client side by using JavaScript.	How Does It run - when you deploy a Farm solution, It gets deployed to one or more web apps (any existing or new one). You can use it in any site collection of the web app where you deployed it.
Authentication options - Before you can call SharePoint APIs from your app, you need to authenticate to SharePoint. Which authentication mechanism you use depends upon where the code of your app is running. * Inside SharePoint: You have to use HTML and JavaScript, and authentication is already taken care for you. * In the cloud: You have two choices: Use client-side code along with the cross-domain library. User server-side code along with OAuth. *REST APIs	Authentication options - The components in the solution can, and usually do, run in full trust
Resource Allocation - Site collection administrators and tenant administrators can monitor apps and change the resources allocated to them.	Resource Allocation - No resource usage restrictions are placed on them
What Can be Created as Apps - Custom Web Parts (remote pages that contain custom Web Parts) Event receivers and Feature receivers(remote event receivers) Custom field (column) types () Custom web services built on the SharePoint Service Application Framework Application pages Cannot be created as Apps - Apps cannot call SharePoint server side code Apps cannot access SharePoint components that are not on the same site Apps cannot communicate with each other Custom site definitions Custom themes Custom action groups and custom action hiding User controls (.ascx files) Delegate controls	What Can be Created as Farm soltuion - You can deploy almost all the components as Farm solution.

Sharepoint 2013 Vs Sharepoint 2010

SharePoint 2013	SharePoint 2010
What is SharePoint 2013 (Preview) - A new version of Microsoft famous Collaboration portal called SharePoint. The version adds few new exciting features such as Social Feed,SharePoint Apps and cross-site publishing.	What is SharePoint 2010 - It is a previous or I should say current version of SharePoint that was released in year 2010.
Development Changes – In SharePoint 2013 Microsoft Introduced a new Cloud App Model for designing Apps for SharePoint. Apps for SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. You can use HTML, CSS, JavaScript and protocols like the Open Data protocol (OData), and OAuth to communicate with SharePoint using Apps. Tools – SharePoint 2013 has Introduced new Tools for App development. Visual Studio 2012 now lets you develop apps for SharePoint and apps for Office. In addition a new web-based tools called “Napa” Office 365 Development Tools were introduced for developing apps. No more Sandbox solutions. SharePoint 2013 sandboxed solutions are deprecated. So all we got is the New App model and the Old SharePoint Farm solutions. check out SharePoint 2013 – Apps Vs Farm solutions	Development Changes – SharePoint 2010 Introduced Sandbox solutions to help developers deploy code that did not effect the whole farm. In SharePoint 2010 you could use Server Object model and Client Object model (.Net Managed, ECMASCRIPT and silverlight) to extract data from SharePoint. In SharePoint 2010 developers were also developing Farm solutions as they did with the previous SharePoint 2007 version.
Social and Collaboration features – Microsoft in SharePoint 2013 Introduced new Social capabilities for better collaboration in the company.New Features added are - Interactive feed Community Site Follow people Follow Sites	Social and Collaboration features - SharePoint 2010 had very few social capabilities. My sites Tags and Tag profile pages Notes
Search - SharePoint 2013 includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Some of the features added are – Consolidated Search Results Rich Results Framework keyword query language (KQL) enhancements	Search – SharePoint 2010 had Introduced Integrated FAST search as an Enterprise search. In addition to this build-in SharePoint search is still widely used in companies.
Enterprise Content Management (ECM) - SharePoint 2013 added some of the best capabilities of an ECM software. The newly added stuff is Design Manager Managed Navigation Cross-site Publishing EDiscovery	Enterprise Content Management (ECM) - SharePoint 2010 on the other hand had Introduced Managed metadata and taxonomy as a part of new ECM benefits for SP 2010. This version did not had Managed Navigation and Cross-site Publishing. SharePoint designer was a primary tool to modify Master pages instead of the new Design Manager.

SharePoint 2013 vs SharePoint 2010

As we know Microsoft has released the next version of SharePoint 2010 which is called as SharePoint 2013(preview), here we will discuss about some new features of SharePoint and some features missed from SharePoint 2010.

1- In SharePoint 2013 a very new thing introduced known as Cloud App Model.
But in SharePoint it was introduced one concept introduced as Sandboxed solutions. You can view this article for more about SharePoint 2010 sandboxed solutions. But in SharePoint 2013 there will be no more sandboxed solutions.

2- SharePoint 2013 has improved Newsfeed than My Site feature in SharePoint 2010. You can see this article for more on Newsfeed in SharePoint 2013.

3- SharePoint 2013 introduced Community Site. As compared to Discussion board in SharePoint 2010, it has more advanced feature.

4- SharePoint 2013 removed meeting workspace site template which was there in SharePoint 2010.

5- SharePoint 2013 made a change in designer also. In SharePoint 2013 it removed the design and split view, only code view is present. But in SharePoint 2010 3 views were present design, code and split.

6- SharePoint 2010 works with and Designer 2010, SharePoint 2013 works with Visual Studio 2012 and SharePoint designer 2013.

7- SharePoint 2010 supports 3.5 but SharePoint 2013 supports 4.5 version of dotnet framework.

8- Web analytics feature of SharePoint 2010 has been removed from SharePoint 2013.

9- Personalization Site site template of SharePoint 2010 has also been removed in SharePoint 2013.

10- Another major feature visual upgrade has been removed in SharePoint 2013. If you want to upgrade from MOSS 2007 to SharePoint 2010, then SharePoint 2010 offers visual upgrade to upgrade.

And finally the look and feel of SharePoint 2013 is a bit lighter than SharePoint 2010.