Triangulating stateful client requests for web applications

A method, comprising:

• receiving, by a load-balancing device communicatively coupled to a cluster comprising a plurality of interconnected processor-based nodes and to a communications network, a client request from a client device via the communications network;
• adding, by the load-balancing device, a request header, comprising a client request identifier uniquely corresponding to the client request, to the client request;
• determining, by the load-balancing device, that a first processor-based node of the plurality of interconnected processor-based nodes is unavailable, wherein the first processor-based node is a primary session node that maintains a primary copy of client session data for the client device;
• responsive to determining that the first processor-based node is unavailable, sending, by the load-balancing device, the client request to a second processor-based node of the plurality of interconnected processor-based nodes for routing to a secondary session node, wherein the second processor-based node is unaffiliated with the client session data for the client device in that the second processor-based node does not store a copy of client session data corresponding to the client request;
• receiving, by the second processor-based node, the client request from the load-balancing device;
• identifying, by the second processor-based node, a third processor-based node of the plurality of interconnected processor-based nodes as the secondary session node that maintains a backup copy of the client session data for the client device;
• and
• sending, by the second processor-based node, the client request to the third processor-based node.

A computer program product stored on a non-transitory computer-readable storage medium and including computer-executable instructions that, when executed, cause one or more processor devices to:

• receive a client request from a client device via a communications network;
• add a request header, comprising a client request identifier uniquely corresponding to the client request, to the client request;
• determine that a first processor-based node of a plurality of interconnected processor-based nodes of a cluster is unavailable, wherein the first processor-based node is a primary session node that maintains a primary copy of client session data for the client device;
• responsive to determining that the first processor-based node is unavailable, send the client request to a second processor-based node of the plurality of interconnected processor-based nodes for routing to a secondary session node, wherein the second processor-based node is unaffiliated with the client session data for the client device in that the second processor-based node does not store a copy of client session data corresponding to the client request;
• receive the client request;
• identify a third processor-based node of the plurality of interconnected processor-based nodes as the secondary session node that maintains a backup copy of the client session data for the client device;
• and
• send the client request to the third processor-based node.