Systems for locating server nodes for edge devices using latency-based georouting

1. A system for locating server nodes for edge devices using latency-based georouting, comprising:

at least one edge device;

a plurality of server nodes; and

at least one cloud platform, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, at least one cloud platform application programing interface (API), a cloud platform scheduler, at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one cloud platform is in network communication with the at least one edge device and the plurality of server nodes;

wherein information associated with each of the plurality of server nodes is stored in the node database on the at least one cloud platform;

wherein the at least one cloud platform is operable to receive an initial hypertext transfer protocol (HTTP) request from the at least one edge device;

wherein the at least one cloud platform router is operable to query the node database;

wherein node data is fetched from each of the plurality of server nodes using an object-oriented function, and wherein the object-oriented function is a serverless function;

wherein the at least one cloud platform router is operable to send a query result to the at least one edge device, and wherein the query result indicates a nearest node from the plurality of server nodes for the at least one edge device;

wherein the at least one cloud platform router is operable to send a response to the HTTP request to the at least one edge device, and wherein the response includes a unique hypertext markup language (HTML) web page; and

wherein an execution of the HTTP request is performed by the at least one edge device using the nearest node.

2. The system of claim 1 , wherein the execution of the HTTP request using the nearest node is performed in parallel with the response to the HTTP request with the unique HTML web page.

3. The system of claim 1 , wherein the unique HTML web page is populated with a subset of the node data from the plurality of server nodes.

4. The system of claim 1 , wherein the nearest node is selected based on a geolocation for the at least one edge device and/or a latency value corresponding to the at least one edge device.

5. The system of claim 1 , wherein each of the plurality of server nodes is registered in a cloud platform global registry using an HTTP POST request to a global service address, and wherein the cloud platform registry is associated with the at least one cloud platform.

6. The system of claim 1 , wherein the plurality of server nodes are microservers operable to form a global peer-to-peer (P2P) network.

7. The system of claim 1 , wherein each of the plurality of server nodes contains a node identifier (ID), an Internet Protocol (IP) address, a set of global positioning system (GPS) coordinates, a central processing unit (CPU) ID, a version number, an uptime value, a node heartbeat value, an edge executor, a plurality of v8 isolates, and/or time zone data.

8. A system for locating server nodes for edge devices using latency-based georouting, comprising:

at least one edge device;

a plurality of server nodes; and

at least one cloud platform, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, at least one cloud platform application programing interface (API), a cloud platform scheduler, at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one cloud platform is in network communication with the at least one edge device and the plurality of server nodes;

wherein information associated with each of the plurality of server nodes is stored in the node database on the at least one cloud platform;

wherein the at least one cloud platform is operable to receive an initial hypertext transfer protocol (HTTP) request from the at least one edge device;

wherein the at least one cloud platform is operable to query the node database;

wherein the at least one cloud platform router is operable to send a query result to the at least one edge device, and wherein the query result indicates a nearest node from the plurality of server nodes for the at least one edge device;

wherein a unique hypertext markup language (HTML) web page is populated with a subset of node data from the plurality of server nodes;

wherein the at least one cloud platform router sends a response to the HTTP request to the at least one edge device, and wherein the response includes the unique HTML web page; and

wherein an execution of the HTTP request is performed by the at least one edge device using the nearest node.

9. The system of claim 8 , wherein the execution of the HTTP request using the nearest node is performed in parallel with the response to the HTTP request with the unique HTML web page.

10. The system of claim 8 , wherein the nearest node is selected based on a geolocation for the at least one edge device and/or a latency value corresponding to the at least one edge device.

11. The system of claim 8 , wherein the plurality of server nodes are microservers operable to form a global peer-to-peer (P2P) network.

12. The system of claim 8 , wherein the unique HTML web page contains at least one object-oriented function, and wherein the at least one object-oriented function is a serverless function.

13. The system of claim 8 , wherein each of the plurality of server nodes contains a node identifier (ID), an Internet Protocol (IP) address, a set of global positioning system (GPS) coordinates, a central processing unit (CPU) ID, a version number, an uptime value, a node heartbeat value, an edge executor, a plurality of v8 isolates, and/or time zone data.

14. A system for locating server nodes for edge devices using latency-based georouting, comprising:

at least one edge device;

a plurality of server nodes; and

at least one cloud platform, wherein the at least one cloud platform includes a cloud platform domain name system (DNS) service, at least one cloud platform application programing interface (API), a cloud platform scheduler, at least one cloud platform router, a cloud platform database, a node database, and a cloud platform storage component;

wherein the at least one cloud platform is in network communication with the at least one edge device and the plurality of server nodes;

wherein each of the plurality of server nodes is registered in a cloud platform registry using a hypertext transfer protocol (HTTP) POST request to a global service address, and wherein the cloud platform registry is associated with the at least one cloud platform;

wherein information associated with each of the plurality of server nodes is stored in the node database on the at least one cloud platform;

wherein the at least one cloud platform is operable to receive an initial HTTP request from the at least one edge device;

wherein the at least one cloud platform router is operable to query the node database using the at least one cloud platform router;

wherein the at least one cloud platform router is operable to send a query result to the at least one edge device, and wherein the query result indicates a nearest node from the plurality of server nodes for the at least one edge device;

wherein the at least one cloud platform router is operable to send a response to the HTTP request to the at least one edge device, and wherein the response includes a unique hypertext markup language (HTML) web page; and

wherein an execution of the HTTP request is performed by the at least one edge device using the nearest node.

15. The system of claim 14 , wherein the HTTP POST request includes a globally unique identifier (GUID), a latitude, a longitude, a zip code, a street address, CPU information, a version number, an uptime, a time zone, and an Internet Protocol (IP) address.

16. The system of claim 14 , wherein the execution of the HTTP request using the nearest node is performed in parallel with the response to the HTTP request.

17. The system of claim 14 , wherein the unique HTML web page contains at least one object-oriented function, and wherein the at least one object-oriented function is a serverless function.

18. The system of claim 14 , wherein the nearest node is selected based on a geolocation for the at least one edge device and/or a latency value corresponding to the at least one edge device.

19. The system of claim 14 , wherein the plurality of server nodes are microservers operable to form a global peer-to-peer (P2P) network.

20. The system of claim 14 , wherein each of the plurality of server nodes contains a node identifier (ID), an Internet Protocol (IP) address, a set of global positioning system (GPS) coordinates, a central processing unit (CPU) ID, a version number, an uptime value, a node heartbeat value, an edge executor, a plurality of v8 isolates, and/or time zone data.