SharePoint Server Side Object model Vs Client Side Object model

This is a very common question which comes to developers mind that when should you use client side object model and when should you use server side model. Before starting about the differences between client side and server side model, lets first understand the working of client side object model.

Working of Client Object Model

When you use the client side API SharePoint managed client object model creates an XML of these API uses and sends it to the SharePoint server. SharePoint server receives the request and make the appropriate calls into object model on the server and collect the responses. After collecting the responses server forms them into JSON and sent it back to SharePoint managed client object model.The client object model parses the JSON and presents the results to the application as .NET Framework objects.

http://msdn.microsoft.com/en-us/library/office/ee857094(v=office.14).aspx

Client Object Model

With the SharePoint managed client object model, you can design client applications that access SharePoint content without installing code on the SharePoint server.
Provides limited options as compared to the server object model. Infact client  object model is the sub set of server side model.

Client object model APIs are wrappers around the custom Web service that calls the server object model.

Client object model execute commands in a batch of command. It also gives the better performance then server object model.

Server Object Model

With the SharePoint server side model, you have to deploy the code packet SharePoint server.

Provides extensive properties and methods to work with SharePoint content.