OCI Load Balancer and traffic management

Load Balancer

  • Application Loadbalancer / Network Loadbalancer
  • Network-based load balancer works on TCP/UDP/ICMP
  • App-Based load Balancer works on Application Layer [Http/Https]
  • Load Balancer Public [Comes with Public IP] and Private [With private Ip]
  • Task: service discovery, health check, Algorithm
  • Flexible Shape  or Dynamic Shape
  • Layer 4 or Layer 7 LB
  • You can attach NSG, by default not enabled
  • LB can be attached to only one subnet
  • You can enable WAF at LB
  • Listener  : [Same AWS target group]
    • Weighted round-robin [Round robin with weighted distribution]
    • Ip Hash  [Bound Ip to make a request to the same server]
    • Least request [Redirect Request to the server which has the least number of conenction]
  • Up to 16 Listener, 4-state health checks, updated every 3 minute
  • There can be downtime in change shape as the existing connection will be drained
  • Health Check status
    • OK
    • INVALID_STATUS_CODE
    • TIMEOUT 
    • REGEX_MISMATCH
    • IO_ERROR
    • OFFLINE
    • UNKNOW
  • Route based on Virtual Hostname or path-based routing

OCI Traffic Management and Health Checks

  • A global Service, generally used in DR/HA to perform Request regional Request Routing

Traffic Management

  • Policy
    • Load Balancer [weighted based load balancing]
    • Failover
    • Geolocation Steering
    • ASN Steering
    • IP Prefix Steering

Health check

  • Health Check is available for any public ip available [LB, Compute etc]
  • Check the target from different Vantage points
  • HTTP based health check  or ping type monitors
  • Performance monitoring from response time
  • Failover detection
  • Hybrid Monitoring

Sources Load balancer

Leave a Reply

Your email address will not be published. Required fields are marked *