This pattern provides an opportunity for a more effective Model-Viewer-Controller (MVC) implementation. With application logic centered in the browser, the model aspect of MVC becomes the remotely linked aspect of the equation rather than the viewer and controller. The model can potentially be more automated for performance improvement than the viewer and controller, which require significant programmatic consideration for efficiency.

Traditional web applications have fallen very easily into the flaw of keeping transient application state on the server. Session variables/objects have lulled many programmers into this trap, which violates the REST principles of the HTTP protocol, and leads to significant memory loads on servers, and prevents caching opportunities. Fat clients on the otherhand naturally tend to store transient application state information on the browser, and can access server side data with idempotent requests very naturally.

Also, this pattern can potentially reduce server processing load. If the majority of processing occurs on the client, than less load is placed on the server, and it can scale to more users more effectively. Generally most client machines have plenty of unused computing capability to take advantage of (effectively distributing the load web applications).