The Oracle Bare Metal Cloud Load Balancing Service provides automated traffic distribution from one entry point to multiple application servers while increasing capacity (concurrent users) and reliability of applications. Here is the brief description of benefits, limitations and load balancing policies of Oracle Cloud Load Balancing Service.
- Load balancer improves resource utilization, facilitates scaling, and helps ensure high availability.
- You can configure multiple load balancing policies
- You can perform application-specific health checks to ensure that the load balancer directs traffic only to healthy instances.
- The load balancer can reduce your maintenance window by draining traffic from an unhealthy application server before you take it offline for maintenance.
- You cannot dynamically change the load balancer shape to handle additional incoming traffic.
- The Load Balancing Service does not support IPv6 addresses.
- The load balancer is limited to 100,000 concurrent connections.
- Outbound traffic to the internet is limited to 2 Gbps.
- Each load balancer has the following configuration limits:
- One public IP address
- 16 backend sets
- 512 backend servers per backend set
- 1024 backend servers total
- 16 listeners
Load Balancing Policies
You can apply following policies to control traffic distribution to your backend application servers.
- Least Connections: The Least Connections policy routes incoming non-sticky request traffic to the backend server with the fewest active connections.
- Round Robin: Round Robin is the default load balancer policy. This policy distributes incoming traffic sequentially to each server in a backend set list.
- IP Hash: The IP Hash policy uses an incoming request’s source IP address as a hashing key to route non-sticky traffic to the same backend server.