A method for operating a distributed application includes: transmitting, by an application frontend of the distributed application, upon a launch of the application frontend, an initialization request to a registration server via a communication network; selecting, by the registration server, upon receipt of the initialization request, an instance of an application backend of the distributed application and transmitting an IP address of the selected instance to the application frontend; transmitting, by the application frontend, upon receipt of the IP address, application data to the transmitted IP address via a connection provided by the communication network; selecting, by a core server of the communication network, upon transmission of the application data, a quality service for the distributed application; applying, by the communication network, a service quality determined by the selected quality service to the connection; and operating the distributed application with the applied service quality.

Systems for locating server nodes for edge devices using latency-based georouting. At least one cloud platform including at least one cloud platform router and a node database is in network communication with at least one edge device and a plurality of server nodes. The at least one cloud platform receives an initial hypertext transfer protocol (HTTP) request from the at least one edge device. The node database is queried using the at least one cloud platform router and node data is fetched from the plurality of server nodes using an object-oriented function. A query result is returned indicating a nearest node from the plurality of server nodes. The HTTP request is responded to with a unique hypertext markup language (HTML) web page, and the HTTP request is executed using the nearest node.

Systems for locating server nodes for edge devices using latency-based georouting. At least one cloud platform including at least one cloud platform router and a node database is in network communication with at least one edge device and a plurality of server nodes. The at least one cloud platform receives an initial hypertext transfer protocol (HTTP) request from the at least one edge device. The node database is queried using the at least one cloud platform router and node data is fetched from the plurality of server nodes using an object-oriented function. A query result is returned indicating a nearest node from the plurality of server nodes. The HTTP request is responded to with a unique hypertext markup language (HTML) web page, and the HTTP request is executed using the nearest node.

Apparatuses, methods, and systems are disclosed for supporting edge data network discovery. One apparatus includes a transceiver and a processor that receives a first request from a function in the mobile communication network including a UE identity and a UE network address. The processor determines whether the UE is located in a first service area based on a UE location and forwards a DNS request received from the UE network address to a first DNS server associated with the first service area in response to determining that the UE is located in the first service area. Via the transceiver, the processor receives a DNS reply from the first DNS server and sends a second request to a policy function in the mobile communication network in response to determining that the DNS reply includes a first IP address.

Apparatuses, methods, and systems are disclosed for supporting edge data network discovery. One apparatus includes a transceiver and a processor that receives a first request from a function in the mobile communication network including a UE identity and a UE network address. The processor determines whether the UE is located in a first service area based on a UE location and forwards a DNS request received from the UE network address to a first DNS server associated with the first service area in response to determining that the UE is located in the first service area. Via the transceiver, the processor receives a DNS reply from the first DNS server and sends a second request to a policy function in the mobile communication network in response to determining that the DNS reply includes a first IP address.

Systems and methods for cloud-based hybrid service meshes in microservice architectures are disclosed. A method for selection of a microservice in a cloud-based hybrid mesh microservice architecture may include: (1) receiving, at a hybrid service mesh library in a first microservice instance, a request for a second microservice, wherein the hybrid service mesh library comprises microservice information for a plurality of microservice instances comprising an identification of each microservice instance, a location for each microservice instance, and a status for each microservice instance; (2) identifying, by the hybrid service mesh library, a number of microservice instances for the microservice and the location of each microservice instance; (3) selecting, by the hybrid service mesh library, one of the plurality of microservice instances; and (4) calling, by the hybrid service mesh library, the selected microservice instance.

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

A computing system providing virtual computing services may maintain a fleet of servers that host virtual machine instances having a wide variety of types and configurations. A service provider may rent processor and memory capacity by defining and offering various virtual machine instances to clients. Each virtual machine instance may include one or more virtual CPUs and a fixed amount of virtualized memory allocated to each virtual CPU, dependent on a predefined ratio between virtual CPU capacity and virtualized memory capacity for the instance type. Each server may include a custom, non-standard sized physical memory module containing memory devices of multiple technologies, types, or sizes on the same printed circuit board. By including custom memory modules, rather than relying only on standard memory modules, the service provider system may implement virtual machines having finer grained options for processor and memory capacity combinations, and may avoid stranding rentable resources.

A computing system providing virtual computing services may maintain a fleet of servers that host virtual machine instances having a wide variety of types and configurations. A service provider may rent processor and memory capacity by defining and offering various virtual machine instances to clients. Each virtual machine instance may include one or more virtual CPUs and a fixed amount of virtualized memory allocated to each virtual CPU, dependent on a predefined ratio between virtual CPU capacity and virtualized memory capacity for the instance type. Each server may include a custom, non-standard sized physical memory module containing memory devices of multiple technologies, types, or sizes on the same printed circuit board. By including custom memory modules, rather than relying only on standard memory modules, the service provider system may implement virtual machines having finer grained options for processor and memory capacity combinations, and may avoid stranding rentable resources.

A DNS resolution request for a hostname of a CDN is received. An edge server of the CDN may be identified, which may be associated with a subnet. The subnet is used to generate a response IP address, where the remaining bits of the response IP address may be used to store requestor information (e.g., a requestor IP address). When a client computing device uses the response IP address to access the edge server, requestor information is extracted and associated with client computing device information (e.g., an IP address and/or location, etc.) in an association record. Association records may be used to determine predicted characteristics for devices served by a requestor. When the authoritative DNS server resolves a request from the requestor, such predicted characteristics may be used rather than relying solely on information about a requestor. Thus, an edge server proximate to the predicted location may be returned instead.