# Choose whether cluster compute and storage should scale together

> Should a planned failover cluster add compute and storage in the same growth unit?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:15:39+00:00
- Modified: 2026-09-08T18:20:22+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## What you need to know

Should a planned failover cluster add compute and storage in the same growth unit?

## Potentially affected

Architects comparing Windows Server failover-cluster storage layouts.

## DSE recommendation

Compare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage.

## Article

## Source facts

Microsoft distinguishes storage separated from compute from hyperconverged Storage Spaces Direct. With separate SAN or NAS storage, cluster nodes reach storage across a network and compute and storage can grow independently. In the hyperconverged model, Storage Spaces Direct combines drives from the nodes into a shared pool and exposes Cluster Shared Volumes. Adding nodes increases compute resources and storage together. [Microsoft documentation](https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures).

## Applicability

Start with workload growth, storage growth, existing equipment, and ownership requirements. Check the applicable hardware and operating-system requirements for each proposed design before treating a diagram as an approved configuration.

## DSE recommendation

Compare two concrete expansion scenarios: adding capacity without additional application compute, and adding compute without additional storage. Record which servers, fabric components, and owners participate in each option. Ask application and storage teams to agree on the expansion unit and the maintenance responsibilities it creates.

## Verification

Review a representative workload placement and maintenance event against the selected architecture. Confirm where its data resides, which nodes can reach it, and how expansion would be performed under the approved design. Keep capacity assumptions and measured application requirements explicit so later growth does not rely on an undocumented architectural shortcut.

## Official references

[Microsoft Learn: Failover Clustering Storage Architectures in Windows Server](https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures). Source reviewed September 8, 2026.

## Primary reference

- Name: Failover Clustering Storage Architectures in Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/failover-clustering/storage-architectures
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Choose whether cluster compute and storage should scale together,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-092-choose-whether-cluster-compute-and-storage-should-scale-together/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.