Client-side versus Server-side Programming

• All-Client, All-Server or Some-of-Both   Expand (p)

In client-server applications in general, and web applications in particular, you have a choice as to where your code should execute. One can design a web application such that all the code runs on the server's CPU. Or you can have all the code execute on the client's CPU. Or, more likely, some combination of the two.

• Benefits of Client-Side   Expand (ul)
• Can result in fewer network calls.
• Can reduce the load on the server in some cases.
• Can provide a more responsive user interface (for example with form validation and animation).
• Benefits of Server-Side   Expand (ul)
• More reliable (due to browser comapatibity issues).
• Large programs can be too slow to download to the browser and are thus best left on the server.
• It is sometimes better to have the code execute closer to the data on which it is executing.
• Certain features, libraries or APIs may not be avaialable in client-side programming tools.
• Since client-side code runs on the user's pc and could pose a security threat, client-side code is often severly restricted (by browser security managers) in what it can do.