In general, embodiments of the present invention provide systems, methods and computer readable media for a universal relevance service framework for ranking and personalizing items.

Some embodiments provide novel methods for performing services for machines operating in one or more datacenters. For instance, for a group of related guest machines (e.g., a group of tenant machines), some embodiments define two different forwarding planes: (1) a guest forwarding plane and (2) a service forwarding plane. The guest forwarding plane connects to the machines in the group and performs L2 and/or L3 forwarding for these machines. The service forwarding plane (1) connects to the service nodes that perform services on data messages sent to and from these machines, and (2) forwards these data messages to the service nodes. In some embodiments, the guest machines do not connect directly with the service forwarding plane. For instance, in some embodiments, each forwarding plane connects to a machine or service node through a port that receives data messages from, or supplies data messages to, the machine or service node. In such embodiments, the service forwarding plane does not have a port that directly receives data messages from, or supplies data messages to, any guest machine. Instead, in some such embodiments, data associated with a guest machine is routed to a port proxy module executing on the same host computer, and this other module has a service plane port. This port proxy module in some embodiments indirectly can connect more than one guest machine on the same host to the service plane (i.e., can serve as the port proxy module for more than one guest machine on the same host).

A novel design of a gateway that handles traffic in and out of a network by using a datapath daemon is provided. The datapath daemon is a run-to-completion process that performs various data-plane packet-processing operations at the edge of the network. The datapath daemon dispatches packets to other processes or processing threads outside of the daemon by utilizing a user space network stack.

Method and apparatus for carrying out the method receiving packets, each of the packets comprising a header and a payload. For a particular packet among the packets, the method includes processing at least the header of the particular packet to determine a flow associated with the particular packet; attempting to determine a payload structure based on the flow, the payload structure associated with transport of coded video data in the payload of the particular packet; and if the attempting is successful, repackaging coded video data contained in the payload of the particular packet into a new packet and forwarding the new packet to an external system or storing the new packet in memory.

A first fabric abstraction layer couples to a data link layer and a physical layer of a network fabric device. The network fabric device is connected to other network elements within a network via at least one network connection, such as a fiber optic connection. A second fabric abstraction layer couples to the data link layer and an application of the network device. The second fabric abstraction layer provides an application programming interface (API) to the application. The API allows the application to generate configuration instructions for configuring the at least one network connection. Upon receiving the configuration instructions generated by the application, the second abstraction layer sends the configuration instructions to the first abstraction layer via the data link layer. The first abstraction layer then configures the at least one network connection to transmit data according to the configuration instructions.

An application programming interface (API) gateway cluster control method includes determining, by an API gateway cluster, that a quantity of API requests received per unit of time exceeds a traffic control parameter, obtaining a load parameter of the API gateway cluster and a load parameter of a service cluster, determining, based on the load parameter of the API gateway cluster, that the API gateway cluster is congested, determining, based on the load parameter of the service cluster, that the service cluster is not congested, and scaling out the API gateway cluster.

An application programming interface (API) gateway cluster control method includes determining, by an API gateway cluster, that a quantity of API requests received per unit of time exceeds a traffic control parameter, obtaining a load parameter of the API gateway cluster and a load parameter of a service cluster, determining, based on the load parameter of the API gateway cluster, that the API gateway cluster is congested, determining, based on the load parameter of the service cluster, that the service cluster is not congested, and scaling out the API gateway cluster.

A communication device receives, using a connectionless protocol, data transmitted by a transmission terminal. The communication device determines, in accordance with a receivable size of the communication device, a data transmission request in order to receive the data from the transmission terminal.

An application programming interface (API) gateway cluster control method includes determining, by an API gateway cluster, that a quantity of API requests received per unit of time exceeds a traffic control parameter, obtaining a load parameter of the API gateway cluster and a load parameter of a service cluster, determining, based on the load parameter of the API gateway cluster, that the API gateway cluster is congested, determining, based on the load parameter of the service cluster, that the service cluster is not congested, and scaling out the API gateway cluster.

An application programming interface (API) gateway cluster control method includes determining, by an API gateway cluster, that a quantity of API requests received per unit of time exceeds a traffic control parameter, obtaining a load parameter of the API gateway cluster and a load parameter of a service cluster, determining, based on the load parameter of the API gateway cluster, that the API gateway cluster is congested, determining, based on the load parameter of the service cluster, that the service cluster is not congested, and scaling out the API gateway cluster.