Abstract: Systems, methods, and other embodiments associated with a highly available network computer system that does not utilize a load balancer are described. In one embodiment, the system includes a plurality of management application instances configured to manage network devices and a plurality of network devices. Each network device includes computer storage medium storing a registry of management application instances. The registry records, for each management application instance, connection information used to communicate with the management application instance and an associated priority for each management application instance. The network device also includes an agent and selection logic. The agent is configured to identify a network communication intended for a management application instance.

Abstract: A system of remote nodes may be divided into sets of partner nodes. One remote node becomes a partner of another remote node. As partners, the nodes agree to monitor each other's health and report anomalies, such as a failure of one of the nodes, to a monitoring server. The nodes do so using a persistent communication link, such as an open socket. Using the described techniques, the monitoring load of a system is distributed in part away from the monitoring server and to the nodes themselves. This may reduce the resources required of the monitoring server. At the same time, since nodes are now being monitored by partner nodes that are likely to be closer than the monitoring server, and/or on account of the monitoring being performed via a persistent communication link, certain failures can be detected in real-time or near real-time.

Abstract: Systems, methods, and other embodiments associated with a highly available network computer system that does not utilize a load balancer are described. In one embodiment, the system includes a plurality of management application instances configured to manage network devices and a plurality of network devices. Each network device includes computer storage medium storing a registry of management application instances. The registry records, for each management application instance, connection information used to communicate with the management application instance and an associated priority for each management application instance. The network device also includes an agent and selection logic. The agent is configured to identify a network communication intended for a management application instance.

Abstract: A system of remote nodes may be divided into sets of partner nodes. One remote node becomes a partner of another remote node. As partners, the nodes agree to monitor each other's health and report anomalies, such as a failure of one of the nodes, to a monitoring server. The nodes do so using a persistent communication link, such as an open socket. Using the described techniques, the monitoring load of a system is distributed in part away from the monitoring server and to the nodes themselves. This may reduce the resources required of the monitoring server. At the same time, since nodes are now being monitored by partner nodes that are likely to be closer than the monitoring server, and/or on account of the monitoring being performed via a persistent communication link, certain failures can be detected in real-time or near real-time.