Clustering Nirvana servers

Nirvana supports clustering through its sophisticated name space. A Nirvana name space can contain one or more Nirvana message servers, each one containing many topics, queues or Peer 2 Peer services.

The Nirvana namespace is fully federated and can be traversed in any direction from any point. Each Nirvana server is aware of each other and each one can redirect clients automatically to the required resource thus providing alternative routes when network outages occur. There is no single point of entry to a clustered Nirvana namespace.

The entry into a Nirvana name space or server is via a custom URL called an RNAME. The RNAME provides the protocol, host and port required to access the Nirvana server. Nirvana clients can be passed an array of RNAME’s. Should a connection fail to one the Nirvana client automatically moves onto the next.

The remote management of clustered server is enabled via the Nirvana administration tool. There is no limit placed on the number of Nirvana Realms that can be managed from the administration tool. The screenshot below shows a Nirvana namespace where a Realm called 'Europe' has been added to the 'globalforexb2b' Realm at the mountpoint '/eu'.

For more example of adding Nirvana Realms into a Nirvana namespace please see the following

Adding a Nirvana Realm to a namespace programatically

Adding a Nirvana Realm to a namespace using the Realm Manager GUI

add Realm example code.

In the screen shot below the Nirvana namespace consists of two Nirvana Realms where a Realm used for channels relating to Europe has been mounted into the namespace under the /eu name. Any client connected to the golbalforexb2b Realm will have access to all resources (provided they are permissioned appropriately) on the Europe Realm under the name /eu. For example to subscribe to the european orders channel they would simply subscribe to a channel called /eu/orders.

The namespace also contains a P2P chat service called Inter-broker-chat.