Abstract: Systems, methods, and computer program products are directed to machine learning techniques that use a separate embedding layer. This can allow for continuous monitoring of a processing system based on events that are continuously generated. Various events may have corresponding feature data associated with at least one action relating to a processing system. Embedding vectors that correspond to the features are retrieved from an embedding layer that is hosted on a separate physical device or a separate computer system from a computer that hosts the machine learning system. The embedding vectors are processed though the machine learning model, which may then make a determination (e.g. whether or not a particular user action should be allowed). Generic embedding vectors additionally enable the use of a single remote embedding layer for multiple different machine learning models, such as event driven data models.

Abstract: In one embodiment, a method includes sending, through a communications network, several volumes of notifications corresponding to a first notification type to multiple users and several volumes of notifications corresponding to a second notification type to multiple users. The method further determines visitation impacts of the volumes of notifications of the first and second notification types and trains a machine-learning model based on the visitation impacts. The machine-learning model generates an assessment of a likelihood of interaction by a recipient user with each of the notifications.

Abstract: In one embodiment, a method includes sending, through a communications network, several volumes of notifications corresponding to a first notification type to multiple users and several volumes of notifications corresponding to a second notification type to multiple users. The method further determines visitation impacts of the volumes of notifications of the first and second notification types and trains a machine-learning model based on the visitation impacts. The machine-learning model generates an assessment of a likelihood of interaction by a recipient user with each of the notifications.

Abstract: The obtaining of a lease on a resource in a circumstance in which multiple lease servers are capable of granting a lease to the resource. A computing entity attempts to obtain the lease on the resource by causing a lease request to be sent to each of at least most (and perhaps all) of the lease servers. In response, the computing entity receives one or more responses to the lease requests. If the computing entity receives grants of a lease from a majority of the lease servers that are capable of granting a lease to the resource, then it is determined that the computing entity acquired a lease on the resource. On the other hand, if the computing entity receives grants of a lease from less than a majority of the lease servers, it is determined that the computing entity failed to acquire the lease on the resource.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: The obtaining of a lease on a resource in a circumstance in which multiple lease servers are capable of granting a lease to the resource. A computing entity attempts to obtain the lease on the resource by causing a lease request to be sent to each of at least most (and perhaps all) of the lease servers. In response, the computing entity receives one or more responses to the lease requests. If the computing entity receives grants of a lease from a majority of the lease servers that are capable of granting a lease to the resource, then it is determined that the computing entity acquired a lease on the resource. On the other hand, if the computing entity receives grants of a lease from less than a majority of the lease servers, it is determined that the computing entity failed to acquire the lease on the resource.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: A load balancer that is able to detect and mitigate a Denial of Service (DOS) attack. The load balancer is placed in the flow path of network data packets that are destined for one or more tenant addresses. The load balancer analyzes performance parameters regarding the network data packets that are destined for the one or more tenant addresses and are received at the load balancer. The performance parameters describe network data packet flow to the tenant addresses. The load balancer detects, based on the analysis of the performance parameters, that one or more of the tenant addresses are being subjected to a DOS attack. The load balancer performs a mitigation operation to isolate the one or more tenant addresses being subjected to the DOS attack.

Abstract: A central NAT manager efficiently allocates ports to endpoints of a tenant application in a hosting environment for NAT purposes. In some instances, the central NAT manager may pre-allocate ports to endpoints as part of the initial configuration of the tenant application. The pre-allocation process may include persisting pre-allocated port state information in storage and configuring endpoints and a NAT device with the pre-allocated port state information. Additional ports may be dynamically allocated to endpoints during runtime using dynamically determined port allocation sizes. In other instances, the central NAT manager may reserve ports for endpoints during the initial configuration of the tenant application by assigning ports to endpoints and persisting port assignment information to storage. During runtime, endpoints may issue port allocation requests to the central NAT manager, which may allocate ports to the endpoints from the range of ports initially reserved for each endpoint.

Abstract: A load balancer that is able to detect and mitigate a Denial of Service (DOS) attack. The load balancer is placed in the flow path of network data packets that are destined for one or more tenant addresses. The load balancer analyzes performance parameters regarding the network data packets that are destined for the one or more tenant addresses and are received at the load balancer. The performance parameters describe network data packet flow to the tenant addresses. The load balancer detects, based on the analysis of the performance parameters, that one or more of the tenant addresses are being subjected to a DOS attack. The load balancer performs a mitigation operation to isolate the one or more tenant addresses being subjected to the DOS attack.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: Load balancing for single-address tenants. When a load balancer detects that a virtual address is associated with a single destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a plurality of destination addresses. The load balancer instructs the router to bypass the load balancer for network packets that are addressed to the virtual address, and refrains from storing subsequent flow state for the virtual address. When the virtual address is to be scaled up with an additional destination address, the load balancer sets a flag to distinguish the virtual address from virtual addresses that are associated with a single destination addresses. The load balancer instructs the router to route network packets that are addressed to the virtual address through the load balancer, instead of bypassing the load balancer, and starts storing flow state for the virtual address.

Abstract: A central NAT manager efficiently allocates ports to endpoints of a tenant application in a hosting environment for NAT purposes. In some instances, the central NAT manager may pre-allocate ports to endpoints as part of the initial configuration of the tenant application. The pre-allocation process may include persisting pre-allocated port state information in storage and configuring endpoints and a NAT device with the pre-allocated port state information. Additional ports may be dynamically allocated to endpoints during runtime using dynamically determined port allocation sizes. In other instances, the central NAT manager may reserve ports for endpoints during the initial configuration of the tenant application by assigning ports to endpoints and persisting port assignment information to storage. During runtime, endpoints may issue port allocation requests to the central NAT manager, which may allocate ports to the endpoints from the range of ports initially reserved for each endpoint.