Systems and methods providing serverless dns integration

A system comprising:

• one or more processor;
• and
• a computer readable medium storing instructions which, when executed by the one or more processor, cause the one or more processor to perform operations comprising:
• receiving, via an application programing interface (API) and from one of an internal client or an external client, a domain name system request;
• communicating the domain name system request to a domain name system;
• notifying an orchestrator system of data associated with the domain name system request, wherein the data indicates that the orchestrator system needs to quickly spin up a function associated with an entity comprising one of a virtual machine, one or more containers or a physical node according to:
• (1) a geographic component which can impact a location of the entity as being closer to an existing function or a client that made the domain name system request and (2) a function distribution algorithm, operated by the orchestrator system, that implements a chosen pattern of distributing functions across nodes based on domain name system requests and system usage;
• provisioning, by the orchestrator system and based on the data and the geographic component and the chosen pattern of distributing functions across nodes, the function on the entity;
• notifying a load balancer regarding the entity operating the function, wherein the load balancer is a separate device from the domain name system;
• providing a response to the domain name system request;
• receiving an API request from one of the internal client or the external client and via the API;
• when the API request is from the external client, routing, via the API, the API request directly to the load balancer and routing, by the load balancer, the API request associated with the domain name system request to the entity;
• and
• when the API request is from the internal client, routing, via the API, the API request from the internal client to the entity.

A non-transitory computer-readable storage device storing instructions which, when executed by one or more processors, cause is the one or more processors to perform operations comprising:

• receiving, via an application programing interface (API) and from one of an internal client or an external client, a domain name system request;
• communicating the domain name system request to a domain name system;
• notifying an orchestrator system of data associated with the domain name system request, wherein the data indicates that the orchestrator system needs to quickly spin up a function associated with an entity comprising one of a virtual machine, one or more containers or a physical node according to:
• (1) a geographic component which can impact a location of the entity as being closer to an existing function or a client that made the domain name system request and (2) a function distribution algorithm, operated by the orchestrator system, that implements a chosen pattern of distributing functions across nodes based on domain name system requests and system usage;
• provisioning, by the orchestrator system and based on the data and the geographic component and the chosen pattern of distributing functions across nodes, the function on the entity;
• notifying a load balancer regarding the entity operating the function, wherein the load balancer is a separate device from the domain name system;
• providing a response to the domain name system request;
• receiving an API request from one of the internal client or the external client and via the API;
• when the API request is from the external client, routing, via the API, the API request directly to the load balancer and routing, by the load balancer, the API request associated with the domain name system request to the entity;
• and
• when the API request is from the internal client, routing, via the API, the API request from the internal client to the entity.