Web Infrastructure  «Prev 

The Role the Object Request Broker plays within the context of CORBA

Question: What role does the Object Request Broker play within the context of CORBA? The Object Request Broker (ORB) plays a central role in the Common Object Request Broker Architecture (CORBA). The ORB is responsible for enabling communication and data exchange between distributed objects in a CORBA system. The ORB acts as a middleware layer that sits between the client and server applications, providing a standard interface for remote method invocation and object sharing. When a client application needs to invoke a method on a remote object, it sends a request to the ORB. The ORB then locates the appropriate server application and sends the request to the server. The ORB also handles other tasks related to distributed object communication, such as data marshalling and unmarshalling, object activation and deactivation, and transaction management. It provides a layer of abstraction that enables client and server applications to interact with each other in a platform-independent manner.
The ORB is a key component of the CORBA architecture, providing a standard mechanism for distributed object communication that can be used across different programming languages, platforms, and systems. The ORB allows developers to build distributed applications using a modular, component-based approach, where objects can be shared and reused across different applications and systems. In summary, the Object Request Broker (ORB) plays a crucial role in the CORBA architecture, enabling communication and data exchange between distributed objects in a standardized, platform-independent manner. The ORB provides a layer of abstraction that simplifies the development of distributed applications and allows for greater interoperability between different systems and applications.


The ORB facilitates the deployment and management of CORBA
1) The ORB facilitates the deployment and management of CORBA, COM+, and Java objects across different architectures.

Using ORBs, the developer of a multi-object application can easily partition those objects onto different networks nodes.
2) Using ORBs, the developer of a multi-object application can easily partition those objects onto different networks nodes. It is therefore like the RPC-based approach, except its object, not function, oriented. As such, it makes object methods available at run-time rather than at design-time.

So while remote objects are designed differently, they share a common language, which enables them to operate with one another.
3) So while remote objects are designed differently, they share a common language, which enables them to operate with one another. Sometimes this language is known as IDL (interface definition language).

The ORB world has a few major standards, most notably including the Object Management Group.
4) The ORB world has a few major standards, most notably including the Object Management Group. (CORBA) Common Object Request Broker Architecture, its internet implementation which is IIOP, as well as Microsoft's standard .NET Services.