Distributed Objects Computing: The next generation of client-server computing
Software technology is in the midst of a
major computational shift towards distributed object computing DOC. Distributed computing is poised for a second
client-server revolution, a transition from first generation client-server era
to the next generation client-server era. In this new client-server model,
servers are plentiful instead of scarce(because every client can be a server)
and proximity no longer matters. This immensely expanded client-server model is
made possible by the recent exponential network growth and the progress in
network-aware multithreaded desktop operating systems.
In the
first generation client-server era, which still is very much in progress, SQL
databases, transaction processing (TP) monitors, and groupware have begun to
dispatch file servers as client-server application models. In the new
client-server era, DOC is expected to dominate other client-server application
models.
Distributed objects are reusable software components that can be distributed and
accessed by the user across the network. These objects can be assembled into
distributed applications. DOC introduces
a higher level of abstraction into the distributed applications.
Distributed
object technology has been tied to standards from the early stage. Since 1989,
the Object Management Group(OMG), with over 500 member companies, has been
specifying the architecture for an open software bus on which object components
written by different vendors can operate across networks and operating systems.
The OMG and the object bus are well on their way to becoming the universal
client-server middleware.
Currently
there are several competing DOC standards, including the OMG’s CORBA, OpenDoc
and Microsoft’s ActiveX/DCOM. Although DOC technology offers unprecedented
computing power, few organizations have been able to harness it as yet.
The main reasons commonly cited for slow adoption of DOC include closed legacy
architecture, incompatible protocols, inadequate network bandwidths and
security issues.
0 Comments