Sign in Subscribe

CORBA (Common Object Request Broker Architecture)

Last updated on 

CORBA (Common Object Request Broker Architecture) is an architecture that provides a standard way for objects to communicate with each other across different platforms, programming languages, and networks. It was developed in the early 1990s by the Object Management Group (OMG), a non-profit consortium of industry and academic organizations that develops and maintains standards for distributed computing.

The goal of CORBA is to allow objects to communicate with each other as if they were on the same computer, even if they are distributed across a network or use different programming languages. This is achieved by using a middleware layer called an Object Request Broker (ORB) that manages the communication between objects.

CORBA is designed to be a platform-independent, language-independent, and network-independent architecture. It supports a wide range of programming languages, including C++, Java, Python, and more, and can work over different types of networks, such as TCP/IP, ATM, and more.

Components of CORBA

There are several components in a CORBA architecture. These include:

Object Request Broker (ORB)

The Object Request Broker is the middleware component that manages the communication between objects. It is responsible for locating objects, sending requests to them, and receiving responses from them. The ORB is responsible for ensuring that the objects are able to communicate with each other, regardless of their location, programming language, or platform.

Object Services

Object Services are a set of standardized services that can be used by CORBA objects. These services include naming, security, persistence, and transaction management. Object Services provide a standardized way for objects to access common functionality across different platforms and programming languages.

Interface Definition Language (IDL)

The Interface Definition Language (IDL) is a language-independent way of defining the interface of an object. It specifies the operations that the object can perform, as well as the data types that it uses. IDL allows objects to communicate with each other without knowing the implementation details of the other object.

Object Adapter

The Object Adapter is responsible for adapting CORBA objects to the underlying platform. It provides a bridge between the CORBA object and the platform-specific implementation of the object.

How CORBA works

When two CORBA objects need to communicate with each other, they use the Object Request Broker (ORB) as an intermediary. The ORB acts as a communication hub between the two objects, sending requests and receiving responses.

When a client sends a request to a server, the request is first sent to the client's ORB. The client's ORB then forwards the request to the server's ORB. The server's ORB then locates the server object and sends the request to the object. The server object processes the request and sends a response back to the client through the same ORBs.

CORBA supports synchronous and asynchronous communication. In synchronous communication, the client waits for a response from the server before proceeding. In asynchronous communication, the client does not wait for a response and can continue with other tasks while waiting for the response.

Advantages of CORBA

  1. Platform independence: CORBA provides a platform-independent architecture, allowing objects to communicate with each other regardless of their location, programming language, or platform.
  2. Language independence: CORBA supports a wide range of programming languages, making it easier to develop distributed systems using different languages.
  3. Interoperability: CORBA allows objects to communicate with each other even if they are running on different platforms or using different programming languages.
  4. Standardization: CORBA provides a standardized way of defining object interfaces and services, making it easier to develop and maintain distributed systems.
  5. Scalability: CORBA supports distributed computing, allowing systems to be scaled up as needed.

Disadvantages of CORBA

  1. Complexity: CORBA is a complex architecture that can be difficult to implement and maintain. It requires a lot of expertise and resources to design and implement a CORBA system.
  2. Performance: The use of middleware in the communication process can lead to additional overhead and slower performance compared to direct communication between objects.
  3. Cost: Implementing a CORBA system can be expensive, as it requires the use of specialized middleware and tools. It may also require significant investment in training and development.
  4. Compatibility: There may be compatibility issues between different versions of CORBA or between different implementations of the CORBA standard, which can create challenges in maintaining and upgrading systems.
  5. Security: CORBA does not provide built-in security features, so additional security measures must be implemented to ensure the security of the system.

Conclusion

CORBA is a powerful architecture that provides a standardized way of developing distributed systems. It allows objects to communicate with each other across different platforms, programming languages, and networks. Despite its advantages, CORBA is a complex architecture that can be difficult to implement and maintain. It requires a lot of expertise and resources to design and implement a CORBA system. Additionally, the use of middleware in the communication process can lead to additional overhead and slower performance compared to direct communication between objects. Nevertheless, CORBA remains an important technology for developing distributed systems, particularly in legacy systems that still rely on it.