POGO COMPOSABLE INFRASTRUCTURE

Composability vs. Virtualization/Containerization

Take the visual diagram of a glass of orange juice: In virtualization/containerization, the orange juice is provisioned to give multiple users the appearance that several glasses of orange juice are available.

Based on requirements, each user has access to resources without the ability to exceed capacity, nor return underutilized resources during off-peak hours for other users. As a result, virtualization and containerization are great to share a single server and support many users with small enough needs, but not an optimal framework to maximize resource utilization.

The root of composability is the opposite approach of virtualization/containerization: the individual components of a glass of orange juice that make up the whole – the orange juice, straw, slices of orange – are disaggregated into a virtual whole. In composability, a glass of orange juice is customized for each user's unique requirements by taking individual components, such as the orange juice, 2 straws, 5 slices of orange.

The API management software orchestrates the provisioning of the resource pools by composing bare-metal environments – not virtual environments with a hypervisor layer. The hardware elements are separated – CPU’s, NVMe SSD’s, GPU’s, NIC’s and FPGA – and independently assigned into server nodes. Based on hosted application requirements, components can be scaled-up or down, as needs change.