Resource utilization in edge-computing clusters and other computing clusters can be improved according to some aspects described herein. For example, an event handler can detect an event involving a state change to a data object. In response to detecting the event, the event handler can access an event registry storing relationships between a group of controllers and a group of events that are to be handled by the group of controllers. The event handler can determine, using the event registry, a controller that is configured to handle the event. The event handler can then transmit a command over a network to a computing cluster that includes a reconciler associated with the controller, where the command is for causing the reconciler to perform a reconciliation operation with respect to the data object. Separating the event-handling logic from the reconciliation logic in this way may improve resource utilization.

An edge server of a distributed edge compute and routing service receives a tunnel connection request from a tunnel client residing on an origin server, that requests a tunnel be established between the edge server and the tunnel client. The request identifies the hostname that is to be tunneled. An IP address is assigned for the tunnel. DNS record(s) are added or changed that associate the hostname with the assigned IP address. Routing rules are installed in the edge servers of the distributed edge compute and routing service to reach the edge server for the tunneled hostname. The edge server receives a request for a resource of the tunneled hostname from another edge server that received the request from a client, where the other edge server is not connected to the origin server. The request is transmitted from the edge server to the origin server over the tunnel.

An edge server of a distributed edge compute and routing service receives a tunnel connection request from a tunnel client residing on an origin server, that requests a tunnel be established between the edge server and the tunnel client. The request identifies the hostname that is to be tunneled. An IP address is assigned for the tunnel. DNS record(s) are added or changed that associate the hostname with the assigned IP address. Routing rules are installed in the edge servers of the distributed edge compute and routing service to reach the edge server for the tunneled hostname. The edge server receives a request for a resource of the tunneled hostname from another edge server that received the request from a client, where the other edge server is not connected to the origin server. The request is transmitted from the edge server to the origin server over the tunnel.

Some embodiments provide a method for a software-defined wide area network (SD-WAN) connecting first and second sites, with the first site including an edge node and the second site including multiple forwarding hub nodes. At the edge node of the first site, the method receives a packet of a particular flow including a flow attribute. The method uses the flow attribute to identify a hub-selection rule from multiple hub-selection rules, each hub-selection rule identifying at least one forwarding hub node at the second site for receiving one or more flows from the first site, and at least one hub-selection rule identifying at least one forwarding hub node that is not identified by another hub-selection rule. The method uses the identified hub-selection rule to identify a forwarding hub node for the particular flow. The method then sends the packet from the edge node at the first site to the identified forwarding hub node at the second site.

Some embodiments provide a method for a software-defined wide area network (SD-WAN) connecting first and second sites, with the first site including an edge node and the second site including multiple forwarding hub nodes. At the edge node of the first site, the method receives a packet of a particular flow including a flow attribute. The method uses the flow attribute to identify a hub-selection rule from multiple hub-selection rules, each hub-selection rule identifying at least one forwarding hub node at the second site for receiving one or more flows from the first site, and at least one hub-selection rule identifying at least one forwarding hub node that is not identified by another hub-selection rule. The method uses the identified hub-selection rule to identify a forwarding hub node for the particular flow. The method then sends the packet from the edge node at the first site to the identified forwarding hub node at the second site.

Provided are a computer program product, system, and method for estimating resource requests for workloads to offload to host systems in a computing environment. A calculation is made required resources of computational resources required to complete processing a plurality of unfinished workloads that have not completed. A determination is made of allocated resources that are not yet provisioned to workloads. The required resources are reduced by the allocated resources not yet provisioned to determine resources to provision. The resources to provision for the unfinished workloads are requested.

An application context relocation method performed by an edge enabler client (EEC) included in a user equipment (UE) in an edge computing system is provided. The application context relocation method includes determining to request an application context relocation by detecting that the application context relocation is required for a predicted or expected UE location; determining a target edge enabler server (T-EES) by using T-EES information received from an edge data network (EDN) configuration server; transmitting, to a source edge enabler server (SEES), an application context relocation request to start the application context relocation; receiving, from the S-EES, an application context relocation response, in response to the application context relocation request; and receiving, from the S-EES, an application context relocation notification of completion of the application context relocation.

An application context relocation method performed by an edge enabler client (EEC) included in a user equipment (UE) in an edge computing system is provided. The application context relocation method includes determining to request an application context relocation by detecting that the application context relocation is required for a predicted or expected UE location; determining a target edge enabler server (T-EES) by using T-EES information received from an edge data network (EDN) configuration server; transmitting, to a source edge enabler server (SEES), an application context relocation request to start the application context relocation; receiving, from the S-EES, an application context relocation response, in response to the application context relocation request; and receiving, from the S-EES, an application context relocation notification of completion of the application context relocation.

In some implementations, a system may monitor session data associated with a first module and a second module of a platform. The system may determine a rate of communication between the first module and the second module based on the session data. The system may determine, using an optimization model, a co-location score associated with the first module and the second module based on the rate of communication, wherein the co-location score indicates an impact of co-location of the first module and the second module. The system may determine that the co-location score satisfies a co-location score threshold associated with an improvement to an operation of the platform. The system may perform an action associated with co-locating the first module and the second module.

Systems and methods are described herein for streaming during unavailability of a content server. Upon determining that there are conditions indicating buffering issues during delivery of a media asset, a server determines a first group of devices suitable for receiving the media asset from the server and sharing the media asset on a peer-to-peer network. Then, the server determines a second group of devices suitable for receiving the media asset on a peer-to-peer network from a first group device. The server then determines groupings within which to share and receive the media asset. Next, the server transmits instructions to the devices in the first group to maintain in buffer and share certain portions of the media asset with the second group devices within their grouping. Finally, the server updates information detailing the media asset portions the devices are maintaining in buffer and sharing.