Browser/Server(TM) Computing

The Browser/Server Paradigm

Thin Client - platform independent

Business Logic on Server

Central software storage and control

even for user interface

The Browser/Server^TMparadigm of computing has all the advantages of Client/Server without the disadvantages.

The split-up of the corporate applications is different for Browser/Server^TM. The user interface and the data interaction components are still run on the user machine, but the business logic usually remains on the Server, usually in a special Server called an Application Server.

The user interface and data interaction components do run on the Client, but they are not ultimately stored there. They are most probably Java applets stored in a corporate Intranet Web Server, and they are automatically loaded into the Browser software on the user machine as they are needed. If a newer version becomes available, then that version is automatically loaded.

We have achieved the same benefits as with Client/Server, but without the enormous distribution and maintenance problem. The only software that the user machine needs, besides an operating system and personal productivity software, is a Web Browser that runs Java applets.

Since much of the "fat" of the application resides in the business logic Application Server, the need to constantly upgrade the user machines is greatly reduced. There is no need to spend precious time and hard disk space installing corporate software on thousands of user machines, or hundreds of departmental LANs.

Corporate software assets now all reside in corporate servers, under IT control. Updates to systems are now easily coordinated.

[ Next ]