Comparison of DCOM and CORBA distributed computing

The movement of distributed applications from 2-tier to n-tier architectures have enabled systems to be scaled to meet the demands of an ever increasing population of users. Two middleware architectures have come to the forefront: Microsoft\u27s DCOM and the OMG\u27s CORBA. These are not the only possible architectures for n-tier distributed applications, but they are currently the only two which offer a degree of platform independence and the flexibility of using different programming languages for development. CORBA provides platform independence because it provides a middle layer between the client and the server and services client requests using its internal naming service to identify server objects and then expose methods to the client through it\u27s object adapter (POA). CORBA is a self contained middleware that operates independent of the underlying operating system. CORBA offers the potential of ease of maintainability since server objects can be changed and the new methods can be discovered at runtime by the client using CORBAs Dynamic Invocation Interface. Client code would therefore not have be recompiled as it would using static IDL mappings and client and server stubs. DCOM, in contrast is a platform dependent solution that can only be used on Windows machines, although ports for other platforms are in the works. It relies on the Windows registry to identify objects and the operating system to assist in runtime control of objects. Because DCOM is nothing more of a remote extension to the already established Common Object Model which all contemporary Windows operating systems and applications are built upon, it may provide the easiest path to distributed applications for Windows developers that are already familiar with the Common Object Model

Web Based Development Using n-tier Technologies

This report from the Comparison and Evaluation Laboratory (CEL) of the Computer and Information Science department at Temple University compares web-oriented n-tier systems development architectures. The focus is on comparing the Distributed Component Object Model (DCOM) with Java + Common Object Request Broker Architecture (CORBA) approach. The comparison is grounded on the experience of a team solving a benchmark task using both approaches. The benchmark task focuses on creating a browser accessible contact management system that keeps track of the relationships that a large company has with customers, brokers, and individuals. The benchmark task includes elements of transaction processing and workflow that are applicable to many other organizational tasks

Comparative Analysis of Business Object Approaches

This paper presents a comparison of several technologies for developing distributed applications. The specific technologies into consideration are: one focused on COM/DCOM/COM and Microsoft technologies, Internet Explorer and ActiveX - and the other focused on Netscape, CORBA, JAVA/J2EE solutions.integrated technologies, interoperability, distributed systems, components, distributed architecture

Driving continuous improvement

The quality of improvement depends on the quality of leading and lagging performance indicators. For this reason, several tools, such as process mapping, cause and effect analysis and FMEA, need to be used in an integrated way with performance measurement models, such as balanced scorecard, integrated performance measurement system, performance prism and so on. However, in our experience, this alone is not quite enough due to the amount of effort required to monitor performance indicators at operational levels. The authors find that IT support is key to the successful implementation of performance measurement-driven continuous improvement schemes

Software engineering and middleware: a roadmap (Invited talk)

The construction of a large class of distributed systems can be simplified by leveraging middleware, which is layered between network operating systems and application components. Middleware resolves heterogeneity and facilitates communication and coordination of distributed components. Existing middleware products enable software engineers to build systems that are distributed across a local-area network. State-of-the-art middleware research aims to push this boundary towards Internet-scale distribution, adaptive and reconfigurable middleware and middleware for dependable and wireless systems. The challenge for software engineering research is to devise notations, techniques, methods and tools for distributed system construction that systematically build and exploit the capabilities that middleware deliver

How to Use a Desktop Version of a DBMS for Client-Server Applications

DBMS (Data base management systems) still have a very high price for small and middle enterprises in Bulgaria. Desktop versions are free but they cannot function in multi-user environment. We will try to make an application server which will make a Desktop version of a DBMS open to many users. Thus, this approach will be appropriate for client-server applications. The author of the article gives a concise observation of the problem and a possible way of solution