The document discusses three key components: LoadMaster, ARR, and WAP, all of which are related to load balancing and application delivery. LoadMaster serves as an application delivery controller with robust features including traffic switching and caching, while ARR is an IIS extension focused on HTTP request routing with basic load balancing capabilities. WAP, a web application proxy, also requires specific conditions for functionality, mainly limited to HTTP workloads with minimal documentation available.

1. IIS ARR
AND
WAP

2. What is LoadMaster?
• Application delivery controller appliance
• Available as hardware appliance or virtual system
• Wide range of load balancing algorithms
• Can be deployed as highly available pairs
• Can switch traffic based on content
• Includes caching and compression
• Active Directory, RADIUS and two-factor
authentication
• Free version available

3. Feature Comparison
Features LoadMaster IIS ARR WAP
Load Balancing Y Y1 Y1
HTTP based
routing Y Y N
Server Name
Indication Y Y N
Intrusion
Protection Y N N
High Availability
(HA Pair) Y N2 N2
GEO
Functionality Y N N
1 – can load balance HTTP workloads only
2 – requires external mechanism to achieve HA

4. What is ARR?
• IIS Extension designed for request routing (similar to
KEMP’s content switching but not as powerful)
• Performs load balancing functions for HTTP requests only
• Cookie based and host based affinity
• Six load balance algorithms
• Weighed RR, Weighed total Traffic, Least current request,
Server variable hash, Query string hash, Request hash
• Requires external mechanism for high availability
(NLB or HLB)
• Also provides caching functionality

5. What is WAP?
• Web Application Proxy included with Windows Server
2012 R2
• ADFS is hard requirement for installation
• No basic or NTLM pre-authentication
• Requires external mechanism for high availability, no
official guidance for HA exists
• No information on persistence and load balancing
mechanisms
• Seems limited to HTTP based workloads only
• Very thin documentation