01
Active health decisions
Unavailable servers leave the service pool until they satisfy the configured health policy.
Application delivery
Reliable traffic distribution for your applications.
Route requests to healthy servers and scale capacity without exposing private application backends.
Policy-drivenTraffic routing
Health-awareBackend selection
Private-readyIsolated application nodes
Capabilities
Stable service access for changing traffic demand.
Separate client traffic from backend topology and manage routing policy from one control point.
02
Controlled TLS edge
Centralise encrypted entry points while keeping certificate and routing intent explicit.
03
Private backends
Expose one controlled service endpoint while application nodes remain on isolated networks.
Traffic flow
One service endpoint, multiple healthy paths.
Traffic routing follows service policy and current backend health in real time.
- 1
Accept
Receive traffic on the intended public or private listener.
- 2
Evaluate
Apply protocol, policy and current health information.
- 3
Distribute
Send each connection to an eligible backend pool member.
Use cases
Flexible traffic management for modern applications.
Use the same control point for traffic peaks, releases and encrypted application paths.
Variable demand
Add or remove serving nodes while clients keep one stable endpoint.
Elastic pools
Blue/green releases
Shift traffic between application versions with a controlled rollback path.
Release control
TLS edge
Move encrypted session handling away from application logic where appropriate.
Focused backends
BLAZINGLAYER
Strengthen application availability at the traffic layer.
Evaluate load balancing options aligned with listener, backend pool, health check and TLS requirements.
Explore load balancing options