The document describes the load balancer request mechanism process which includes: 1. A user requests a site which gets resolved by DNS to the public IP configured in Cloudflare. 2. The load balancer maps the virtual IP configured in the firewall to the public IP using NAT. 3. The virtual IP is mapped to a server group containing web servers and load balancing methods are applied to distribute requests.

1. Load Balancer Request Mechanism
1. User requests for a site

2. Load Balancer Request Mechanism
Internet
1. User requests for a site

3. Internet
1. User requests for a site
Load Balancer Request Mechanism

4. Internet
DNS
Resolve
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e

5. Internet
FIREWALL
Public IP & Virtual IP
Mapping for the site
NAT
DNS
Resolve
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
3. Virtual IP configured in the Load balancer mapped in Firewall for the resolved Public IP using NAT(Network Address Translation)
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e

6. Internet
FIREWALL
Public IP & Virtual IP
Mapping for the site
NAT
DNS
Resolve
Load Balancer
Virtual IP Configuration Real Server
Server Groups
Web
server1
Web
server2
Web
server3
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
3. Virtual IP configured in the Load balancer mapped in Firewall for the resolved Public IP using NAT(Network Address Translation)
4. Virtual IP is mapped to Server Group, which is group of web servers to apply load balancing routing methodologies
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e

7. Internet
FIREWALL
Public IP & Virtual IP
Mapping for the site
NAT
DNS
Resolve
Load Balancer
Virtual IP Configuration Real Server
Server Groups
Web
server1
Web
server2
Web
server3
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
3. Virtual IP configured in the Load balancer mapped in Firewall for the resolved Public IP using NAT(Network Address Translation)
4. Virtual IP is mapped to Server Group, which is group of web servers to apply load balancing routing methodologies
5. Routing methodologies are least connection, Round Robin, Hash; session persistence should be maintained in the application itself
when least connection and Round robin are used.
6. Each webserver information is also maintained in load balancer as Real Server
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e

8. Internet
FIREWALL
Public IP & Virtual IP
Mapping for the site
NAT
DNS
Resolve
Load Balancer
Virtual IP Configuration Real Server
Server Groups
Web
server1
Web
server2
Web
server3
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
3. Virtual IP configured in the Load balancer mapped in Firewall for the resolved Public IP using NAT(Network Address Translation)
4. Virtual IP is mapped to Server Group, which is group of web servers to apply load balancing routing methodologies
5. Routing methodologies are least connection, Round Robin, Hash; session persistence should be maintained in the application itself
when least connection and Round robin are used.
6. Each webserver information is also maintained in load balancer as Real Server
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e

9. Internet
FIREWALL
Public IP & Virtual IP
Mapping for the site
NAT
DNS
Resolve
Load Balancer
Virtual IP Configuration Real Server
Server Groups
Web
server1
Web
server2
Web
server3
1. User requests for a site
2. DNS gets resolved with Public IP configured in the Cloudflare for the site
3. Virtual IP configured in the Load balancer mapped in Firewall for the resolved Public IP using NAT(Network Address Translation)
4. Virtual IP is mapped to Server Group, which is group of web servers to apply load balancing routing methodologies
5. Routing methodologies are least connection, Round Robin, Hash; session persistence should be maintained in the application itself
when least connection and Round robin are used.
6. Each webserver information is also maintained in load balancer as Real Server
Load Balancer Request Mechanism
C
l
o
u
d
F
l
a
r
e