Layer 4 vs Layer 7 load balancing in HLD - Architecture Patterns Compared

System Overview - Layer 4 vs Layer 7 load balancing

This system demonstrates the difference between Layer 4 and Layer 7 load balancing. It shows how incoming user requests are distributed to backend services either by network-level information (Layer 4) or by application-level data (Layer 7). Key requirements include efficient traffic distribution, scalability, and the ability to handle different routing rules.

Architecture Diagram

User
  |
  v
+-----------------+
|  Load Balancer  |
|  (Layer 4 or 7) |
+-----------------+
  |           |
  v           v
Service A   Service B
  |           |
  v           v
Database    Database

Components

User

client

Sends requests to the system

Load Balancer

load_balancer

Distributes incoming requests to backend services based on Layer 4 or Layer 7 rules

Service A

service

Handles requests routed by the load balancer

Service B

service

Handles requests routed by the load balancer

Database

database

Stores persistent data for services

Request Flow - 6 Hops

User → Load Balancer

Load Balancer → Service A or Service B

Service A or Service B → Database

Database → Service A or Service B

Service A or Service B → Load Balancer

Load Balancer → User

Failure Scenario

Component Fails:Load Balancer

Impact:All incoming user requests fail to be routed, causing complete service outage

Mitigation:Use multiple load balancers with failover or clustering to avoid single point of failure

Architecture Quiz - 3 Questions

Which layer does a Layer 4 load balancer operate on?

A Transport layer (IP and TCP/UDP ports)

B Application layer (HTTP headers and URLs)

C Physical layer (cables and signals)

D Session layer (manages sessions)

Design Principle

This architecture shows how load balancers at different layers affect routing decisions and system flexibility. Layer 4 load balancers are faster but less flexible, while Layer 7 load balancers enable smarter routing based on application data but add processing overhead. Redundancy in load balancers is critical to avoid single points of failure.

Practice

1. Which layer does Layer 4 load balancing operate on?

easy

A. Network layer using routing tables

B. Application layer using request content

C. Transport layer using IP and port

D. Physical layer using hardware signals

Solution

1. Step 1: Understand OSI layers relevant to load balancing

   Layer 4 corresponds to the transport layer, which handles IP addresses and ports.

2. Step 2: Match Layer 4 load balancing function

   Layer 4 load balancing uses IP and port information to distribute traffic without inspecting content.

3. Final Answer:

   Transport layer using IP and port -> Option C

4. Quick Check:

   Layer 4 = Transport layer [OK]

Hint: Layer 4 uses IP and port, Layer 7 uses content [OK]

Common Mistakes:

• Confusing Layer 4 with Layer 7
• Thinking Layer 4 inspects request content
• Mixing network and transport layers

2. Which of the following is a correct characteristic of Layer 7 load balancing?

easy

A. Routes traffic based on IP address only

B. Does not inspect HTTP headers

C. Is faster than Layer 4 load balancing

D. Operates at the application layer inspecting request content

Solution

1. Step 1: Identify Layer 7 load balancing features

   Layer 7 load balancing works at the application layer and inspects request content like HTTP headers.

2. Step 2: Evaluate options

   Operates at the application layer inspecting request content correctly states Layer 7 inspects request content; others are incorrect or misleading.

3. Final Answer:

   Operates at the application layer inspecting request content -> Option D

4. Quick Check:

   Layer 7 = Application layer content inspection [OK]

Hint: Layer 7 inspects content, Layer 4 does not [OK]

Common Mistakes:

• Assuming Layer 7 ignores HTTP headers
• Believing Layer 7 is faster than Layer 4
• Confusing IP-based routing with content-based routing

3. Given a load balancer that routes requests based on URL paths, which layer is it operating at?

medium

A. Layer 2

B. Layer 7

C. Layer 4

D. Layer 3

Solution

1. Step 1: Understand URL path inspection

   URL paths are part of the application data in HTTP requests, which Layer 7 can inspect.

2. Step 2: Match to OSI layer

   Layer 7 is the application layer that can route based on URL paths, unlike lower layers.

3. Final Answer:

   Layer 7 -> Option B

4. Quick Check:

   URL path routing = Layer 7 [OK]

Hint: URL path routing means Layer 7 [OK]

Common Mistakes:

• Choosing Layer 4 for URL-based routing
• Confusing network layers with application layer
• Ignoring request content in routing decisions

4. A system uses a load balancer that inspects HTTP headers but is running slower than expected. What is a likely cause?

medium

A. Layer 7 load balancing adds processing overhead due to content inspection

B. Using Layer 4 load balancing instead of Layer 7

C. Layer 4 load balancing inspects too many headers

D. Layer 7 load balancing does not support IP-based routing

Solution

1. Step 1: Identify load balancer type and performance impact

   Layer 7 load balancing inspects request content like HTTP headers, which adds processing overhead.

2. Step 2: Analyze options for cause of slowness

   Layer 7 load balancing adds processing overhead due to content inspection correctly explains that Layer 7's content inspection slows processing; others are incorrect.

3. Final Answer:

   Layer 7 load balancing adds processing overhead due to content inspection -> Option A

4. Quick Check:

   Content inspection causes slower Layer 7 [OK]

Hint: Content inspection slows Layer 7 load balancers [OK]

Common Mistakes:

• Blaming Layer 4 for inspecting headers
• Ignoring processing overhead of Layer 7
• Assuming Layer 7 cannot route by IP

5. You need to design a scalable web service that routes requests based on user authentication tokens in HTTP headers and also requires high throughput. Which load balancing approach is best?

hard

A. Layer 7 load balancing to inspect tokens despite some overhead

B. Layer 4 load balancing for speed, ignoring tokens

C. Use DNS round-robin instead of load balancers

D. Combine Layer 2 switching with Layer 3 routing

Solution

1. Step 1: Identify requirement to inspect authentication tokens

   Authentication tokens are in HTTP headers, requiring application-level inspection.

2. Step 2: Choose load balancing approach balancing inspection and throughput

   Layer 7 load balancing inspects headers and supports smart routing, suitable despite overhead.

3. Step 3: Evaluate other options

   Layer 4 cannot inspect tokens; DNS round-robin lacks smart routing; Layer 2/3 unrelated to content inspection.

4. Final Answer:

   Layer 7 load balancing to inspect tokens despite some overhead -> Option A

5. Quick Check:

   Token inspection needs Layer 7 [OK]

Hint: Inspect tokens? Use Layer 7 despite overhead [OK]

Common Mistakes:

• Choosing Layer 4 ignoring token inspection need
• Using DNS round-robin for smart routing
• Confusing network layers with application logic