Client Centric vs Server Centric

Server-Centric: In the server centric approach, the generation of the markup and java script (if any) will be
generated by the server. The business logic and the visual logic will be executed in the server. Below are the
advantages of the server centric approach.

Advantages aka Pros:

1. In server-centric business logic and visual logic are executed in server
2. The server generates markup and/or JavaScript
3. No need of JavaScript programming
4. Data and visual state are together
5. Safer
6. Better options for freedom of web design (templates)
7. Easier Search Engine Optimization compatibility

Disadvantages aka Cons:
1. Because in the server-centric business logic and visual logic are executed in server, so for every
validation or execution of the business logic, the application needs to send the request to the server. This
will increase the network bandwidth usage.
2. Because the server will take the responsibility of the generating the mark up and the java script then, the
data that is been returning from the server is very huge.
3. The view state is being stored on the page to maintain the state of the page, the view state data will be
transmitted between the post backs.

Client-Centric: In the client centric approach, the generation of the markup and java script (if any) will be
generated in the client itself. The business logic and the visual logic will be executed in the client. Below are the
advantages of the server centric approach.

Advantages aka Pros:

1. As the markup and the java script are residing in the client, there will not be huge network traffic for the
application.
2. Huge Java script programming must be needed.
3. View state is not available in this approach, so the page will have less weight.
4. Rich User Interface can be designed with the help of the java script tools.
5. Animations and vector graphics will be implemented with ease.

Disadvantages aka Cons:
1. Because in the development will include huge java script files need to be generated. This will reduce the
performance of the developer.
2. It is unmanageable when the code is growing like anything.
3. It is Not Typed, Not Compiled, and Not a true OOP style of programming.
4. It is very hard to organize.
5. It is very hard to test and debug.