Please enable JavaScript.

Coggle requires JavaScript to display documents.

Design new solutions -load balancers (Important Notes (maintainability…

- - - - process in load balancer which check connection request with load balancer
    - - one listener can associated with multiple target groups
      - listeners associated with target groups
  - - - path based
        
        forward traffic to appropriate target based on path mentioned in request URI
      - host based
        
        forward traffic to appropriate target based on host header received for request
- - - - recommended for path based routing
  - - - earlier generation load balancers
      - not recommended
      - only needed if instance is in old Ec2 classic network
      - IP as Target not supported
    - - recommended when protocol is TCP
- - - - it will distribute traffic evenly across multiple backend instances in all AZ. If we don’t check this option while configuring LB then LB will consider AZ as one single large instance. It is better practice to select this option while configuring EL
  - - - path based routing not suppported
      - IP as a target not supported
      - does not support Http/2
    - - advantages
        
        enable path,host based routing
  - - - not possible to support multiple SSL certificates
      - possibility of wild card certificates
    - - can be integrated with cloud trail logs security analysis
  - - - provisioning
      - active
      - terminated
    - - classic load balancer work on round robin fashion
      - NLB works on flow-hash algorithm