How to load-balance Orbix 3 connections
How to load-balance Orbix 3 invocations
How to load-balance with Orbix 3

There are two approaches to load-balancing with Orbix 3: "Server Activation Modes" and "Naming Service Object Groups".

 

 

For more information on these, please see the relevant sections of our documentation, detailed below.

 

 

Server Activation Modes:

 

  Orbix 3.x provides a number of different server activation modes, which specify how the Orbix Daemon manages processes to handle incoming requests.

 

  The following server activation modes are supported by Orbix:

 

  Shared Activation Mode (Default Mode):

    All of the objects with the same server name on a given machine are managed by the same server process on that machine.

 

    When an operation is invoked on the CORBA object, the Orbix Daemon will route it to the one processes associated with the server for that object. If this process is not running, the Orbix Daemon will launch it.

 

 

  Unshared Activation Mode:

 

    Each CORBA object, irrespective of server, is managed by an individual processes.

 

 

    When an operation is invoked on the CORBA object, the Orbix Daemon will route it to the one processes associated with that object. If this process is not running, the Orbix Daemon will launch it.

 

 

  Per-method call Activation Mode:

 

    Each CORBA request, irrespective of object, is managed by an individual processes.

 

    When an operation is invoked on the CORBA object, the Orbix Daemon will launch a new process to handle it.

    

 

 

Naming Service Object Groups:

 

 

  The CORBA Naming Service defines a repository of names that map to objects. Each name maps to one object. OrbixNames extends the CORBA Naming Service model to allow a name to map to a group of objects.

 

  An object group is a collection of objects mapped to a particular name. Each object group has a selection algorithm, which is applied when a client resolves the name associated with the object group. Two algorithms are supported: round-robin selection and random selection.  

 

  The above approach allows client connections to be load-balanced across a number of server objects.