# Decide whether Windows Network Load Balancing fits the application

> When is a Windows NLB cluster an appropriate application distribution choice?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-163-decide-whether-windows-network-load-balancing-fits-the-application/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:28+00:00
- Modified: 2026-09-08T18:26:31+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

When is a Windows NLB cluster an appropriate application distribution choice?

## Potentially affected

Administrators evaluating Windows Network Load Balancing for server applications.

## DSE recommendation

Prepare a short selection record comparing the documented NLB use case with the actual workload.

## Article

## Source facts

Windows NLB combines multiple application servers into one virtual cluster and distributes incoming requests among those servers. Microsoft identifies stateless applications, including IIS web servers, as a practical use case. Its guidance directs SDN deployments, non-Windows workloads, outbound NAT requirements, and certain non-TCP load-balancing requirements toward Software Load Balancer instead. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/networking/technologies/Network-Load-Balancing).

## Applicability

Record the application protocol, server platform, session behavior, and networking design before selecting NLB. Ask the application owner to describe any state that must survive a host becoming unavailable. Do not substitute a network feature overview for that application-specific assessment.

## DSE recommendation

Prepare a short selection record comparing the documented NLB use case with the actual workload. Name the application instances and decide how their readiness will be evaluated. Define a maintenance exercise that removes one host while representative users continue working. Set an acceptance threshold for the application transaction, with a clear owner for investigation if the result differs.

## Verification

Measure completed transactions and errors before, during, and after the approved host-removal exercise. Verify that the remaining hosts receive requests and that the returning host behaves as intended. Include a state-dependent transaction when the application has one. Retain the selected design and rejected alternatives.

## Official references

[Microsoft Learn: Network Load Balancing](https://learn.microsoft.com/en-us/windows-server/networking/technologies/Network-Load-Balancing). Source reviewed September 8, 2026.

## Primary reference

- Name: Network Load Balancing
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/networking/technologies/Network-Load-Balancing
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Decide whether Windows Network Load Balancing fits the application,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-163-decide-whether-windows-network-load-balancing-fits-the-application/
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.