Craig Dunwoody

It is increasingly common to combine as-a-service and as-a-product consumption models for elements of an organization's data infrastructure, including applications; development platforms; databases; and networking, processing, and storage resources. Some refer to this as "hybrid" architecture.

Learning Objectives

A widely used "separate-cluster" architecture for datacenters uses a server cluster, sometimes called a "storage array", that implements highly available shared-storage volumes, and a separate server cluster running application workloads that access those volumes.

An alternative "combined-cluster" architecture, sometimes called "hyperconverged", uses a single server cluster in which every node can participate in implementing highly available shared-storage volumes, and also run application workloads that access those volumes.

Every datacenter includes a set of software and hardware infrastructure building blocks assembled to provide data storage, processing, and networking resources to a set of application workloads. New types of workloads, and new Commercial Off-The-Shelf infrastructure building blocks, are being developed at an increasing rate.

It is increasingly common to combine as-a-service and as-a-product consumption models for elements of an organization's data infrastructure, including applications; development platforms; databases; and networking, processing, and storage resources. Some refer to this as ""hybrid"" architecture.

A widely used "separate-cluster" architecture for datacenters uses a server cluster, sometimes called a "storage array", that implements highly available shared-storage volumes, and a separate server cluster running application workloads that access those volumes. An alternative "combined-cluster" architecture, sometimes called "hyperconverged", uses a single server cluster in which every node can participate in implementing highly available shared-storage volumes, and also run application workloads that access those volumes.