[ad_1]
An object request broker (ORB) acts as a mediator between a client and server, routing requests to the appropriate termination point on the network. ORBs are part of the larger Common Object Request Broker Architecture (CORBA) and can provide multiple termination points for data. They are adaptable and can be configured to handle various client requests.
An object request broker or ORB is programming protocols that work as an intermediary or broker between a customer and a supplier. Using an object request broker, the client sends a request to perform some type of service. The broker receives the request and routes it to a termination point on the network where the request can be completed successfully. By using an object request broker, the client server processing the request does not need to know where to forward the request on the network. The broker evaluates the request and then routes it accordingly.
Sometimes it is useful to interpret an object request broker as an example of middleware. In essence, middleware functions as a means of transmitting data from an originating point to a terminating point, rather than transferring data in strictly point-to-point communication. The advantage of this approach is that the middleware is able to qualify incoming data and route it to a portion of the network where it is likely to be processed most efficiently.
The object request broker is part of the larger Common Object Request Broker Architecture, also known as CORBA. It is this broader architecture that allows the object request broker to accurately and quickly process data input from the client and deliver the data to the appropriate system or server on the network. Each component is set up using the interface definition language which allows the cross compiler to identify each currently working component anywhere on the network.
As part of the overall functionality, an object request broker can provide more than one termination point for the data contained in the client request. For example, data can be copied and moved to various servers on the network. Data can be downloaded into a database for further processing while also being added to simple files for archiving. Confirmation of completion can occur as part of the overall functionality, as well as allowing the request to be restored to its original form if the sequence does not complete successfully.
Because there is the ability to configure the object request broker to fit a number of environments and handle a wide variety of client requests, programmers are able to tailor the broker to handle any number of single and multiple tasks for the request incoming clients. Brokers are also somewhat adaptable, in that as components are added to the network, they can be named and added to the overall architecture with relative ease.
[ad_2]