Infrastructure Level

Infrastructure Level

The platform can run on bare metal servers or on top of third-party IaaS environments such as OpenStack, vSphere, AWS, Azure, Rackspace and other supported infrastructures.

The number of hardware nodes required in a cluster depends on the expected workload and is typically defined during the onboarding and capacity-planning process.

Hardware Hosts

Hardware Hosts are physical servers or large virtual machines. They can be virtualized using technologies such as KVM, ESXi or Hyper-V.

Physical serversDedicated bare-metal hardware used as the underlying infrastructure layer.
Large virtual machinesVirtualized hosts running on technologies such as KVM, ESXi or Hyper-V.
Cluster capacityThe number of hosts depends on the expected application load and platform sizing requirements.

Container-Based Resource Utilization

The platform divides large physical or virtual servers into smaller isolated virtual containers that are used to build customer environments.

This approach allows infrastructure resources to be shared efficiently across many isolated workloads while maintaining separation between applications.

✓

Efficient infrastructure density

Using isolated containers allows the platform to achieve high infrastructure density and efficient utilization of available CPU, memory and storage resources.

Environment Provisioning

Each environment consists of a collection of isolated virtual containers that provide the software stack and resources required by a particular application.

When a new environment is created, the requested containers are provisioned from a pool of pre-created container templates. This significantly reduces provisioning time and allows even complex environments to become available very quickly.

EnvironmentA set of isolated containers configured together for a specific application.
Container templatesPre-created software-stack templates used to speed up provisioning.
Fast deploymentComplex application environments can be provisioned in a short period because containers are created from prepared templates.
Stack isolationEach software stack runs inside its own isolated container, reducing the risk of one stack affecting another.
Infrastructure level hardware node architecture
Hardware hosts are divided into isolated containers that are used to create application environments.

Key Benefits

  • Can be deployed on bare metal or third-party IaaS infrastructure.
  • Supports both physical servers and large virtualized hosts.
  • Uses isolated containers for efficient infrastructure utilization.
  • Pre-created container templates accelerate environment provisioning.
  • Application stacks are isolated from one another.
  • Infrastructure capacity can be scaled according to expected cluster load.

What’s Next?