Skip to navigation
Network & Security

Load Balancers

An IBEE Solutions Load Balancer distributes incoming traffic across multiple backends so your application stays available when a single server fails or is overloaded. Each load balancer gets a stable endpoint (host and port) that you point your clients or DNS at; the load balancer forwards traffic to healthy backends only.

Layers

Choose the layer when you create the load balancer:

LayerProtocolsUse for
L7 (application)HTTP, HTTPSWeb apps and APIs — path- and header-based routing, sticky sessions, TLS termination
L4 (transport)TCP, TLS passthroughDatabases, message queues, custom TCP protocols, or end-to-end encryption where the backend terminates TLS

Capabilities

CapabilityDetails
BackendsRoute to a service, an ip, or a hostname target — each with its own port and weight
Routing algorithmsround_robin, least_request, random, consistent_hash (Algorithms)
Health checksActive HTTP, HTTPS, or TCP checks with configurable thresholds (Health checks)
TLSManaged certificate termination on L7 HTTPS, or TLS passthrough on L4 (SSL and TLS termination)
Sticky sessionsHeader-based session affinity on L7
RetriesAutomatic retries on 5xx, connection reset, and connect failure
L7 rulesPriority-ordered path-prefix and header-match routing rules
Proxy protocolForward client connection metadata so compatible backends see the original client IP

Endpoint

After creation, the load balancer’s detail page shows its public endpoint — Host, Listener port, and the full Public host URL. Point your application or a DNS record at this endpoint.

Manage load balancers

The portal does not support editing a load balancer after creation. To change backends, routing, health checks, or any other setting, delete the load balancer from the list and create a new one (Create a load balancer).