Explain the Proper Distribution of Functionality and Code

It is important to note that the bandwidth of the server operating system and server processor availability is fixed. The amount of processing capability remains consistent across any number of workstation platforms. Sharing this server bandwidth between multiple fronts - ends (clients) will eventually degrade performance. There is a saturation point (number of stations * load) at which perceptible performance at the workstation will decrease due to the overloading of the server computer. The objective of client/server application designer is to distribute functionality and code so as to avoid this saturation point for all normal case scenarios.

The difficulty lies in determining the saturation point. For instance, some server operating systems are more scalable. By adding more horse-power or addition processors to these systems, the saturation point will change. Careful analysis on the target environments might be needed for fine- tuning finished client - server applications. In addition , some emerging technologies and application have the capability of dynamically the execution location of client - server components. These technologies, by being properly architected, greatly increase the scalability and load balancing of the overall system. A goal of the application developer should be to achieve and ideally balanced machine state, although application distribution will vary from application to application and from developer to developer. The developer should keep in mind that the proper architecture and a careful mix of application functions between server and client will eventually determine the viability of the client - server technology.