Com vs CORBA

Thursday, March 15,200 1

By ish Singh

Introduction:

Com is sometimes referenced as common object model but Microsoft officially callit Component Object Model. microsoft also developed DCOM as an extension of COM. DCOM was designed with Distributed Computing in perspective. CORBA stands for Common Object Request Broker Architecture and developed by Object Management Group (OMG ). COM/DCOM and CORBA among others are object-oriented approaches for the use and development of software components. they are the competing ubuntures for application development in the Client/Server world. these ubuntures support distributed computing and provide support for interoperability and limited portability. distributed computing technologies are necessary for creating flexible Client/Server systems. these distributed objects can exist anywhere on the system as they encapsulate the data and business logic within themselves. as heterogeneous systems are getting more and more popular, distributed objects are also getting popular, as they are really good at connecting these heterogeneous systems.

CORBA and DCOM are both designed for client/server style communication among distributed objects. in both technologies, a client invokes a method that is implemented by a remote object that acts as a server. the interface for such an object providing the service is defined in an Interface Definition Language (IDL ). this keeps the object implementations hidden from the client. both CORBA and COM communications are implemented like RPC and methods of remote objects are invoked on reference. the support for data types in both these technologies is limited to a few data types that can be mapped to multiple programming ages.

Origin:

• COM/DCOM:

Its predecessor Ole (Object Linking and Embedding) was originally used for linking events on Microsoft Win 3.1 OS. COM was developed to integrate components dynamically within a single address space. COM was designed to provide support of dynamic use of Multiple Vendor binary components in one single application. component interactions are based on ole2 interfaces and protocols. although com uses ole2 interfaces and protocols, it is worthy to know that com is not Ole. DCOM was developed as an extension of COM to allow Network Based Interactions and allows processes to be spread internal ss a network.

• CORBA:

Common Object Request Broker Architecture was developed by Object Management Group (OMG ). OBG is a consortium of hundreds of companies that are working to the adapt a standard architecture for Distributed Object Computing. CORBA is based on object management architecture, which was published in 1991 by the OMG. CORBA was developed to provide vendors with a standard architecture that allows them to develop applications using different versions, operating systems, and hardware and still provide the portability and interoperability.

Technical View:

• COM/DCOM:

COM allows clients to invoke services provided by com-compliant components by defining a binary compatibility specification and implementation. com compliant components (COM objects) provide a set of interfaces that allow a client to contact the object using those interfaces only.

COM defines the binary structure between the client and the objects and is the basis for interoperability between components written in multiple programming languages as long as the language compiler supports Microsoft program com binary structure.

COM objects can have multiple interfaces but each class must have its own unique class ID (CLSID) and its interface must have globally unique identifier (guid) to avoid name collisions. objects and interfaces are defined using Microsoft semantic IDL (Interface Definition Language ). com architecture does not allow for easy modification of the interfaces and their methods to help prevent potential version incompatibilities. com developers are rather encouraged to build new interfaces to the objects to provide additional functionality. COM objects run inside of a server, and the server provides three ways for the clients to access COM objects.

1. In-process server: client and server run in the same memory process and communicate among each other using function CILS.
2. Local object Proxy: This allows clients using an inter-process communication mechanism to access server running in a different process but on the same physical machine. this inter-process mechanic is also known as lightweight Remote Procedure Call.
3. Remote proxy object: This allows clients to access remote servers running on another machine. clients and servers communicate using distributed computing environment rpc. remote objects supporting this machism are called DCOM servers.

Two major extensions to com: MTS and MSMQ are provided by DCOM. DCOM server objects provide support for multiple threads. MTS (Microsoft Transaction Server) runs on Windows NT Server and provides transaction oriented processing and is based on the DTC (Distributed Transaction Coordinator ). MTS is wrongly ded in DCOM as a runtime middle-ware environment that provides asynchronous Application Operation with MSMQ and synchronous operation with RPC (Remote Procedure Call ). DCOM also has remote garbage collection functionality built into it, which makes it a robust system.

• CORBA:

CORBA is designed and structured to allow integration of multiple object systems written in different versions ages and running on different platforms. CORBA relies on ORB middle-ware for communication between the server and the client. orb acts as an object that connects remote objects transparently. each CORBA object exposes an interface that has a set of methods attached to it. orb is responsible for finding the object implementation for the request and to format and communicate request to the CORBA server. ORB provides transparency to the client, and the client never needs to know about the location of the remote object and what language was used to implement it.

CORBA is based on object management architecture (OMA), and OMA defines a broad range of services for building distributed applications. oma services are divided into three layers named corbaservices, corbafacilities, and applicationobjects. orb communication infrastructure is required for applications to access these services. these services are actually definition of different categories of objects in OMA and define a broad range of functionality needed to support distributed applications.

1. Corbaservices: are the necessary building blocks for developing distributed applications. These services provide asynchronous event management, transactions, persistence, concurrency, naming, relationships, and lifecycle management.
2. Corbafacilities: are not necessary for developing distributed applications but can be useful in some cases. These facilities provide information management, system management, task management, and user interface.
3. Applicationobjects: are dedicated to providing service to a class of application or a specific application. These are either basic services, support common facilities or application-specific services.

CORBA interfaces and data types are defined using OMG Interface Definition Language. each interface should methods are also defined using obg idl. IDL is the key part of CORBA architecture that provides mapping of data types between CORBA and programming languages. IDL also allows for easy encapsulation of legacy code. IDL is an object-oriented interface definition language with syntactic similarities with C ++. as all the interfaces are defined in IDL, CORBA specifications allow for client and objects to be written in different versions while keeping the details transparent from each other. CORBA uses IIOP (Internet Inter-ORB Protocol) for communication among various Object Request Brokers using TCP as the network transport.

CORBA components include ORB core, ORB interface, IDL stub, DII (dynamic invocation interface), Object Adaptor, IDL skeletons, and DSI (Dynamic skeleton interface ). CORBA runtime infrastructure (ORB core): Is Vendor Specific and is not defined by CORBA. however, ORB interface is a standard interface to functions provided by all CORBA compliant ORBs. IDL processor generates stubs for each interface. this hides the low-level communication and provides a high-level, object-type specific API. dii is an alternative to the IDL stubs that provides a generic mechanic for constructing requests at run-time. object Adaptor, provides ability to integrate alternative object technologies into the Oma. IDL skeletons are similar to IDL stubs but they provide the server-side (Object implementation ). object Adaptor sends requests to the IDL skeletons, which in turn call, the appropriate methods in the object implementation.

Technical Comparison:

CORBA relies on IIOP for communication with remote objects while DCOM relies on Object Remote Procedure Call (orpc) for the same purpose. CORBA architecture is based on Object Request Broker while DCOM uses com as its basis and for transaction processing it relies on MTS or MSMQ. CORBA specification is not Vendor Specific and hence CORBA applications can run on multiple hardware platforms. on the other hand, DCOM is Microsoft extends proprietary architecture and runs only on hardware supported by Microsoft operating systems. CORBA allows for multiple inheritance While DCOM only provides single inheritance. DCOM uses Ping every two minutes to check if the client is still alive, if for six minutes the client doesn has respond DCOM discards the client has request. CORBA on the other hand does not force the client to stay connected and does not use keep alive messaging. as DCOM uses keep alive messaging it is able to determine when to discard the request and it has built in garbage collection, while CORBA does not provide built in garbage collection mechanism.

Usage View:

• COM/DCOM:

COM/DCOM is Microsoft extends proprietary architecture and is only supported on Windows family of operating systems. however, third party vendors provide support for DCOM on UNIX systems. DCOM is based on native binary format hence offers faster execution but is not portable to other platforms. COM/DCOM components have access to Windows API and can potentially damage or compromise User Login computing environment. DCOM provides basic support for distributed objects but no support for real time processing or situations requiring high reliability. although COM has been available for a while it is not clear weather its flavor DCOM will be equally valid tive in widely distributed applications.

• CORBA:

CORBA is only a specification and not an implementation, so it usually hard for buyers to determine if the product in consideration is fully CORBA compliant or not. also there are no defined test suites for determining CORBA compliance. it is necessary for users to perform hands-on evaluation of vendor products. CORBA is complex specification and require a considerable expertise for develop distributed objects and applications. on the other hand, it is easier than previusly available technologies for developing distributed applications. still thorough expertise in Distributed Systems Design, distributed and multi-threaded programming and debugging, inter-networking, object oriented design, analysis, and programming is required.

Usage comparison:

Cross-platform support is very extensive in CORBA while COM/DCOM is limited to Microsoft operating systems. CORBA as well as com support components written in multiple ages. CORBA objects are based on a standard specification published in 1991 while COM has specifications and code are continuously changing and the specified ENTs are available only in draft format. COM was originally designed to run on single machine and was not designed for large-scale networks. however, CORBA was designed from scratch with large-scale distributed applications in consideration.

CORBA products are available from a wide variety of vendors while COM/DCOM is only available from Microsoft. as CORBA specification is defined by OMG a consortium of 800 + companies, its highly likely to reflect the demands of the industry as opposed to COM/DCOM, which is proprietary to Microsoft and Microsoft retains the final say in COM/DCOM specifications.

 

Conclusion:

COM/DCOM and CORBA are both scalable and robust ubuntures for Distributed Computing and offer different advantages. however, due to their inherent differences they are suitable for different sizes and types of applications and scenarios. COM/DCOM is suitable if the systems are predominantly running Microsoft extends operating systems and the geographic distribution is not very wide spread. CORBA is suitable for heterogeneous and widely distributed systems. both technologies have similarities and differences in their architecture and hence shoshould be considered before choosing either one. also, specified vendors are offering solutions that allow CORBA applications to interact with COM and vise versa. seems like COM/DCOM and CORBA will continue to compete vigorously and still co-exist for a long time to come.

Reference:

Microsoft Corporation (2001). COM specification.

Tallman, O., & kain, J. (1998). com versus CORBA: A demo-framework.

Brake, M. (1998). Fig.

Object Management Group (2001). The Common Object Request Broker: Architecture and specification.

Microsoft Corporation (1998). Microsoft Component services.

Raj, J. (1998). Common Object Request Broker Architecture.

Software Engineering Institute (1997). Component Object Model (COM), DCOM, and related capabilities.

Software Engineering Institute (1997). Common Object Request Broker Architecture.

Microsoft Corporation (1996). DCOM technical overview.