Summary
The general procedure is:
- Create a VCN with at least two (2) subnets
- Create at least two (2) instances in the private subnet
- Create a load balancer in the public subnet
- Create a backend set that include the instances created above
- Create a listener for the load balancer
Reference
Lab
This topic is covered in Lab 5-1: Networking: OCI Load Balancer:
Load Balancer
The OCI Load Balancer provides automated traffic distribution from one entry point to multiple back-end servers in your VCN. It operates at the connection level and balances incoming client connections to healthy back-end servers. The service offers a load balancer with your choice of a regional public or private IP address and provisioned bandwith.
Summary of Components for OCI Load Balancer Used in This Lab
- Listener: A logical entity that checks for incoming traffic on the load balancer's IP address
- Back-end server: An application server responsible for generating content in reply to the incoming traffic
- Back-end set: A load-balancing ploicy tells the load balancer how to distribute incoming traffic to the back-end servers
- Health check: A test to confirm the availability of back-end servers
- Shape: The Bandwidth capacaity of the load balancer