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

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

at least one cloud platform in network communication with at least one edge device;

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

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

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

wherein the HTTP request is sent to the at least one cloud platform API;

wherein the at least one cloud platform API queries the node database;

wherein the node database sends a node database query response to the at least one cloud platform API, wherein the node database query response contains a unique hypertext markup language (HTML) web page and a nearest node from the plurality of server nodes;

wherein the at least one cloud platform API sends a HTTP query response to the at least one edge device based on the node database query response;

wherein the HTTP query request is executed using the nearest node; and

wherein the API query to the node database includes a set of API query parameters, wherein the set of API query parameters includes a geolocation for the at least one edge device, wherein the geolocation for the at least one edge device is appended to the set of API query parameters to a Uniform Resource Identifier (URI).

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

3. The system of claim 1 , wherein 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.

4. The system of claim 1 , wherein the at least one cloud platform API includes a Representational State Transfer (REST) interface.

5. The system of claim 1 , wherein the at least one cloud platform distinguishes between successful HTTP requests and unsuccessful HTTP requests when calculating a latency, a download speed, a download time, an upload speed, and/or a response time for the nearest node.

6. The system of claim 1 , wherein the HTTP query request is validated and recorded to a blockchain.

7. The system of claim 1 , wherein the node database is a relational database.

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

9. The system of claim 1 , wherein the plurality of server nodes includes at least one microserver.

10. The system of claim 1 , wherein the plurality of server nodes is registered in a cloud platform 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.

11. 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.

12. A system for locating server nodes for edge devices using georouting, comprising:

at least one cloud platform in network communication with at least one edge device;

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

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

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

wherein the HTTP request is sent to the at least one cloud platform API;

wherein the at least one cloud platform API queries the node database;

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 node database sends a node database query response to the at least one cloud platform API, wherein the node database query response contains the unique HTML web page and a nearest node from the plurality of server nodes;

wherein the at least one cloud platform API sends a HTTP query response to the at least one edge device based on the node database query response;

wherein the HTTP query request is executed using the nearest node, 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; and

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. A system for locating server nodes for edge devices using georouting, comprising:

at least one cloud platform in network communication with at least one edge device;

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

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

wherein 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;

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

wherein the HTTP request is sent to the at least one cloud platform API;

wherein the at least one cloud platform API queries the node database;

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 node database sends a node database query response to the at least one cloud platform API, wherein the node database query response contains the unique HTML web page and a nearest node from the plurality of server nodes;

wherein the at least one cloud platform API sends a HTTP query response to the at least one edge device based on the node database query response; and

wherein the HTTP query request is executed using the nearest node, 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.

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

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

16. The system of claim 13 , 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.

17. The system of claim 13 , wherein the plurality of server nodes is operable to form a global peer-to-peer (P2P) network.

18. The system of claim 13 , wherein 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.