Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying one or more pods having multiple containers organized as a cluster in a container system capable of executing the function(s); identifying one or more routing paths in the serverless service architecture, the routing path being associated with one or more serverless execution entities capable of executing the function(s) thereon; determining (i) traffic information on the routing path(s), (ii) a cost or a performance characteristic associated with a computer resource bundle for the pod(s), and/or (iii) a cost or a performance characteristic associated with the serverless execution entity(entities); and based thereon, determining whether to (i) terminate execution of the function(s) on the pod(s) and (ii) cause execution of the function(s) on the serverless execution entity (entities).

Abstract: Various approaches for allocating resources to an application having multiple application components, with at least one executing one or more functions, in a serverless service architecture include identifying multiple routing paths, each routing path being associated with a same function service provided by one or more containers or serverless execution entities; determining traffic information on each routing path and/or a cost, a response time and/or a capacity associated with the container or serverless execution entity on each routing path; selecting one of the routing paths and its associated container or serverless execution entity; and causing a computational user of the application to access the container or serverless execution entity on the selected routing path and executing the function(s) thereon.

Abstract: Systems, methods and apparatus, including computer program products, are disclosed for management of resources and services (e.g., storage, registers, memory, ternary content-addressable memory (TCAM) tables) to route packet sequences in a software-defined networking (SDN) environment. In one embodiment, this management occurs through the use of supply chain economics to manage utilization of TCAM resources.

Abstract: Systems, methods and apparatus, including computer program products, are disclosed for management of resources and services (e.g., storage, registers, memory, ternary content-addressable memory (TCAM) tables) to route packet sequences in a software-defined networking (SDN) environment. In one embodiment, this management occurs through the use of supply chain economics to manage utilization of TCAM resources.