Scalable proxy clusters
The invention enables high-availability, high-scale, high security and disaster recovery for API computing, including in terms of capture of data traffic passing through proxies, routing communications between clients and servers, and load balancing and/or forwarding functions. The invention inter alia provides (i) a scalable cluster of proxies configured to route communications between clients and servers, without any single point of failure, (ii) proxy nodes configured for implementing the scalable cluster (iii) efficient methods of configuring the proxy cluster, (iv) natural resiliency of clusters and/or proxy nodes within a cluster, (v) methods for scaling of clusters, (vi) configurability of clusters to span multiple servers, multiple racks and multiple datacenters, thereby ensuring high availability and disaster recovery (vii) switching between proxies or between servers without loss of session.
1. A method of synchronizing data states between proxy nodes within a networked cluster of proxy nodes, the method comprising:
detecting a synchronization event at a first proxy node within the networked cluster of proxy nodes;
synchronizing, at the first proxy node, one or more data states of the first proxy node with corresponding one or more data states of a second proxy node within the networked cluster of proxy nodes, the one or more data states of the first proxy node and the corresponding one or more data states of the second proxy node including information descriptive of a set of Application Programming Interfaces (APIs) hosted on a set of servers;
reconfiguring, in response to a change to an API from the set of APIs and hosted on a server from the set of servers, the one or more data states of the first proxy node to reflect the change to the API;
communicating, from the first proxy node, the one or more data states of the first proxy node after the reconfiguring to the remaining proxy nodes in the networked cluster of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the one or more data states of the first proxy node, synchronizes one or more data states of that proxy node with the one or more data states of the first proxy node; and
identifying, for each API request from a set of API requests received at the first proxy node, a server from the set of servers to transmit that API request to based on a routing policy and the information descriptive of the set of APIs.
2. The method as claimed in claim 1 , wherein the one or more data states of the first proxy node are synchronized with the one or more data states of every proxy node from the remaining proxy nodes.
3. The method as claimed in claim 1 , wherein the one or more data states of the first proxy node and the corresponding one or more data states of the second proxy node comprise data states of any one or more of server characteristic data, session data, security data, configuration data, or proxy node data associated with the respective proxy node.
4. The method as claimed in claim 1 , wherein the synchronization event includes at least one of:
the first proxy node joining the networked cluster of proxy nodes;
the first proxy node resuming operations subsequent to a state of failure; or
an expiration of a predefined time period.
5. The method as claimed in claim 1 , wherein each API request from the set of API requests is associated with an API from the set of APIs, and the information descriptive of the set of APIs includes information indicating at least one server from the set of servers that hosts each API from the set of APIs,
the identifying including identifying, for each API request from the set of API requests, the at least one server from the set of servers that hosts the API associated with that API request based on the information descriptive of the set of APIs.
6. The method as claimed in claim 1 , wherein the synchronizing the one or more data states of the first proxy node with the corresponding one or more data states of the second proxy node includes configuring the first proxy node to have routing functionality identical to routing functionality of the second proxy node.
7. The method as claimed in claim 1 , further comprising:
receiving, at the first proxy node, a configuration input through at least one of a command-line interpreter (CLI) or a RESTful API;
modifying the one or more data states of the first proxy node in response to receiving the configuration input; and
communicating, from the first proxy node, the one of more data states of the first proxy node after the modifying to the remaining proxy nodes in the networked cluster of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the one of more data states of the first proxy node, synchronizes one or more data states of that proxy node with the one or more data states of the first proxy node.
8. The method as claimed in claim 1 , further comprising:
determining, for each API request from the set of API requests, whether that API request conforms to one or more Layer 7 protocols; and
transmit, in response to determining that an API request from the set of API requests conforms to the one or more Layer 7 protocols, the API request to the server identified for the API request.
9. A computer program product for synchronizing data states between proxy nodes within a networked cluster of proxy nodes, comprising a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code comprising instructions executable to:
detect a synchronization event at a first proxy node within the networked cluster of proxy nodes;
synchronize, at the first proxy node, one or more data states of the first proxy node with corresponding one or more data states of a second proxy node within the networked cluster of proxy nodes, the one or more data states of the first proxy node and the corresponding one or more data states of the second proxy node including information descriptive of a set of Application Programming Interfaces (APIs) hosted on a set of servers;
reconfigure, in response to a change to an API from the set of APIs and hosted on a server from the set of servers, the one or more data states of the first proxy node to reflect the change to the API;
communicate, from the first proxy node, the one or more data states of the first proxy node after the reconfiguring to the remaining proxy nodes in the networked cluster of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the one or more data states of the first proxy node, synchronizes one or more data states of that proxy node with the one or more data states of the first proxy node; and
transmit an API request received from a client device to a server (1) from the set of servers and (2) identified based on a routing policy and the information descriptive of the set of APIs.
10. The computer program product as claimed in claim 9 , wherein the synchronization event includes at least one of:
the first proxy node joining the networked cluster of proxy nodes;
the first proxy node resuming operations subsequent to a state of failure; or
an expiration of a predefined time period.
11. The computer program product as claimed in claim 9 , wherein:
the API request is associated with an API from the set of APIs,
the information descriptive of the set of APIs includes information indicating at least one server from the set of servers that hosts each API from the set of APIs,
the server identified based on the routing policy and the information descriptive of the set of APIs is a server that hosts an API associated with the API request.
12. The computer program product as claimed in claim 9 , wherein the instruction executable to synchronize the one or more data states of the first proxy node with the corresponding one or more data states of the second proxy node includes an instruction executable to configure the first proxy node to have routing functionality identical to routing functionality of the second proxy node.
13. The computer program product as claimed in claim 9 , wherein the computer readable program code further comprises instructions executable to:
modify, in response to receiving a configuration input at the first proxy node through at least one of a command-line interpreter (CLI) or a RESTful API, the one or more data states of the first proxy node to produce one or more modified data states of the first proxy node; and
communicate, from the first proxy node, the one or more modified data states of the first proxy node to the remaining proxy nodes in the networked cluster of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the one of more modified data states of the first proxy node, synchronizes one or more data states of that proxy node with the one or more modified data states of the first proxy node.
14. The computer program product as claimed in claim 9 , wherein the computer readable program code further comprises instructions executable to determine whether the API request conforms to one or more Layer 7 protocols,
the instruction executable to transmit the API request to the server including an instruction executable to transmit the API request to the server in response to determining that the API request conforms to the one or more Layer 7 protocols.
15. An apparatus, comprising:
a memory; and
a processor associated with a proxy node from a plurality of proxy nodes in a cluster of proxy nodes, the processor operatively coupled to the memory and configured to:
synchronize, in response to a synchronization event, a data state of the proxy node with a data state of at least one proxy node other than the proxy node and from the plurality of proxy nodes, the data state of the proxy node and the data state of the at least one proxy node other than the proxy node including information descriptive of a set of Application Programming Interfaces (APIs) hosted on a set of servers;
reconfigure, in response to a change to an API from the set of APIs and hosted on a server from the set of servers, the data state of the proxy node to reflect the change to the API;
communicate the data state of the proxy node that reflects the change to the API to the remaining proxy nodes from the plurality of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the data state of the first proxy node, synchronizes a data state of that proxy node with the data state of the proxy node;
extract, from an API request received from a client device, information descriptive of an API associated with the API request; and
identify a server from the set of servers to transmit the API request to based on (i) the information descriptive of the set of APIs, (ii) the information descriptive of the API associated with the API request, and (iii) a routing policy.
16. The apparatus as claimed in claim 15 , wherein the processor is further configured to:
receive a configuration input through at least one of a command-line interpreter (CLI) or a RESTful API;
modify the data state of the proxy node in response to receiving the configuration input to produce a modified data state; and
communicate the modified data state to the remaining proxy nodes from the plurality of proxy nodes such that each proxy node from the remaining proxy nodes, in response to receiving the modified data state, synchronizes a data state of that proxy node with the modified data state.
17. The apparatus as claimed in claim 15 , wherein the processor is further configured to:
determine whether the API request conforms to one or more Layer 7 protocols; and
transmit, in response to determining that the API request conforms to the one or more Layer 7 protocols, the API request to the server.