Resilient peer-to-peer application message routing

1. A computer-implemented method of performing resilient peer-to-peer application message routing, comprising the steps of:

storing, in a memory, a network routing table comprising destination addresses of destination applications hosted on peer nodes of a network;

registering, by a data processing circuitry including a primary tracker node, a first destination application and a second destination application, where the first destination application is the same as the second destination application and both the first destination application and the second destination application have the same destination address;

providing, by the data processing circuitry including the primary tracker node, the peer nodes and a secondary tracker node with a copy of the routing table, via which routing table, an application message from a query one of the peer nodes is routed to a destination address designating a destination application hosted by a destination peer node;

providing, by the data processing circuitry including the primary tracker node, when the first destination application hosted by the destination peer node is inactivated, all of the peer nodes and the secondary tracker node with a copy of an updated routing table indicating the inactivation of the first destination application and routing of the application message to the second destination application,

wherein a further application message addressed from any of the peer nodes to the destination address associated with the inactivated application is routed, via the updated routing table, to the second destination application having the same destination address as the inactivated application, and

wherein the secondary tracker node, in case of failure of the primary tracker node, performs the providing steps for the primary tracker node including, in response to a request from the querying peer node for a copy of the updated routing table having a most recent version number, providing a copy of the updated routing table having the most recent version number to the querying peer node.

2. The method of claim 1 , wherein the alternative destination application is hosted on the destination peer node which hosted the inactivated application.

3. The method of claim 1 , wherein the alternative destination application is hosted on a peer node different from the peer node which hosted the inactivated application.

4. The method of claim 1 , further comprising:

receiving a notification from one of the primary and secondary tracker nodes that the destination application is inactivated; and

transmitting in response thereto a confirmation that an update of the routing table has been performed taking into account the inactivation of the destination application.

5. A system for facilitating resilient peer-to-peer application message routing, the device comprising:

a storage medium configured to store a network routing table comprising destination addresses of destination applications hosted on peer nodes of a network;

a processor including a primary tracker configured to:

register a first destination application and a second destination application, where the first destination application is the same as the second destination application and both the first destination application and the second destination application have the same destination address; and

provide the peer nodes and a secondary tracker with a copy of the routing table via which routing table an application message from a querying one of the peer nodes is routed to a destination address designating a destination application of a destination peer node,

provide, when the destination application hosted by the destination peer node is inactivated, all peer nodes and the secondary tracker with a copy of an updated routing table indicating the inactivation of the first destination application and routing of the application message to the second destination application,

wherein a further application message addressed from any of the peer nodes to the destination address associated with the inactivated application is routed, via the updated routing table, to an alternative destination application having the same destination address as the inactivated application, and

wherein the secondary tracker is configured to provide the copy of the routing table and provide the copy of the updated routing table in case of failure of the primary tracker node including, in response to a request from the querying peer node for a copy of the updated routing table having a most recent version number, to provide a copy of the updated routing table having the most recent version number to the querying peer node.

6. The system of claim 5 , wherein the alternative destination application is hosted on the destination peer node which hosted the inactivated application.

7. The system of claim 5 , wherein the alternative destination application is hosted on a peer node different from the peer node which hosted the inactivated application.

8. The system of claim 5 , wherein the processor is further configured to:

receive a notification from the destination peer node that the destination application is inactivated; and

transmit, in response thereto, a confirmation that an update of the routing table has been performed taking into account the inactivation of the destination application.

9. The system of claim 5 , wherein the routing table is a hash table.

10. The system of claim 5 , wherein the processor is further configured to provide the copy of the updated routing table in the form of incremental changes with respect to a latest provided copy of the routing table.

11. The system of claim 5 , wherein the processor is further configured to provide the copy of the routing table to the peer nodes of the network for local storage at the respective peer node.

12. A non-transitory, computer-readable medium comprising a computer program which when executed on a computer causes a device to perform the steps recited in claim 1 .