BGTech Content Switching Visual Explainer
The load balancer routes traffic based on request content like URL path
Incoming client request
/api route
/app route
/images route
Client
Sends URL request
Content
Switching
Routing decision
API Backend
Matches: /api/*
Example: /api/users
Web App Backend
Matches: /app/*
Example: /app/home
Static Content Backend
Matches: /images/*
Example: /images/logo.png
Client request arrives
Inspect path
Routing decision
Policy match
/api → API pool
/app → App pool
/images → Static pool
Path: /api/users
Path: /images/logo.png
Path: /app/home
1
Client sends a request
The request reaches one virtual server.
Example URLs may be /api, /app,
or /images.
2
LB checks the content
It inspects request data like URL path,
host header, or file type to decide
where traffic should go.
3
Traffic goes to the right pool
API traffic, app traffic, and static content
can use different backends for cleaner
scaling and simpler design.