OCI Load Balancer

Definition

Oracle's service for distributing traffic across multiple compute instances. Like having a traffic director that ensures no single server gets overwhelmed.

Use Cases

Provider Equivalents

Frequently Asked Questions

What's the difference between OCI Load Balancer and an API Gateway?
OCI Load Balancer primarily spreads network or HTTP(S) traffic across multiple backend servers and checks their health. An API Gateway focuses on managing APIs: routing by API paths, authentication/authorization, rate limiting, request/response transformation, and developer-facing API controls. You often use both: the load balancer for scaling and high availability of web apps, and API Gateway for controlling and securing API access.
When should I use OCI Load Balancer?
Use it when you need high availability and scaling for an application running on multiple backends (compute instances, instance pools, or private IP targets). Common triggers include: you have more than one web/app server, you need health checks and automatic failover, you want TLS termination and centralized certificate management, or you need to expose private backends safely through a single public endpoint.
How much does OCI Load Balancer cost?
Pricing depends on the load balancer shape/capacity and how much data it processes. Key cost drivers typically include: the provisioned bandwidth/capacity (shape), number of load balancer instances, and data processed/egress. Always confirm current rates in the OCI Pricing page for Load Balancing and consider additional costs like public IP usage (if applicable) and outbound data transfer.

Category: networking

Difficulty: intermediate

Related Terms

See Also