Breaking News: Grepper is joining You.com. Read the official announcement!

why not traditional load balancers for service discovery and registration

Add Answer

Anjali Sharma answered on January 6, 2023 Popularity 1/10 Helpfulness 1/10

answer why not traditional load balancers for service discovery and registration

why not traditional load balancers for service discovery and registration

Comment

1. Limited Horinizontal Scalability and license cost

2. Single Point of Failure and centralized choke points\

3. Manually manage the updates in any IPs or configuration

4. Not Container Friendly

5. Complex in Nature

global
    daemon
    maxconn 256

defaults
    mode tcp
    timeout connect 5000ms
    timeout client 60000ms
    timeout server 60000ms

listen http-in
    bind *:80
    server 0_nyc1-worker-1_webapp 162.243.162.228:80 maxconn 32
    server 0_nyc1-worker-2_webapp 162.243.162.226:80 maxconn 32
    server 0_nyc1-worker-3_webapp 162.243.162.229:80 maxconn 32
    server 1_sfo1-worker-1_webapp 107.170.196.151:80 maxconn 32
    server 1_sfo1-worker-2_webapp 107.170.195.154:80 maxconn 32

https://www.hashicorp.com/blog/haproxy-with-consul

Popularity 1/10 Helpfulness 1/10 Language javascript

Source: Grepper

Tags: javascript load registration service-discovery

Link to this answer
Share Copy Link

Contributed on Jan 06 2023

Anjali Sharma

0 Answers Avg Quality 2/10

why not traditional load balancers for service discovery and registration

Contents

More Related Answers

why not traditional load balancers for service discovery and registration

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.