Calling Network Level Load Balancing Guys..

[xxxmen]

VIP vunte u can loadbalance through hw or else you can loadbalance using DNS also

[micxas]

traffic sent to VIP IP will be sent to pool & get load balanced across pool members based on load balancing algorithm choosen (like round robin, least connections etc)

 

pool members- Backend servers  ee kada ?

Algorithm- Yeah got it.

Then where is  the concept of context root coming into picture man? I am aware tht its there at backend servers level, but at load balancer level ?

[micxas]

VIP vunte u can loadbalance through hw or else you can loadbalance using DNS also

Vip name undi man ...  red konchem light vey man , please if you don't mind .. bye1

[harvey]

u will do loadbalcing using ip and port. lets say u have two app server listening on 9080  then u will loadbalnace those two servers using ip and port. Now coming to context root it depends on wht u r loadbalancing. If you are loadbalancing an app server then u need to redirect the call to context root at the loadbalancer level ...lets say for f5 u can write an irule to redirect http call to context root. If you are loadbalancing two apache server then u can have http redirect rules at apache level.

[xxxmen]

Vip name undi man ...  red konchem light vey man , please if you don't mind .. bye1

 

Round robin DNS & DDNS (Dynamic DNS) is often used to load balance requests between a number of Web servers. For example, a company has one domain name and three identical copies of the same web site residing on three servers with three different IP addresses. When one user accesses the home page it will be sent to the first IP address. The second user who accesses the home page will be sent to the next IP address, and the third user will be sent to the third IP address. In each case, once the IP address is given out, it goes to the end of the list. The fourth user, therefore, will be sent to the first IP address, and so forth

[golmaalgovindam]

pool members- Backend servers  ee kada ?

Algorithm- Yeah got it.

Then where is  the concept of context root coming into picture man? I am aware tht its there at backend servers level, but at load balancer level ?

 

irules concept antene context root pettukovachu...so if context root matches....go for this backend anesi.....irules lo you can enable from http to https also.....

 

again am not a loadbalancer expert...nee laage middleware side nenu......wait for others inputs also....

[harvey]

remember one thing only network guys should use the term "VIP" , for all other like middleware admins, developers etc...its just ip. the term vip will confuse you.

[micxas]

u will do loadbalcing using ip and port. lets say u have two app server listening on 9080  then u will loadbalnace those two servers using ip and port. Now coming to context root it depends on wht u r loadbalancing. If you are loadbalancing an app server then u need to redirect the call to context root at the loadbalancer level ...lets say for f5 u can write an irule to redirect http call to context root. If you are loadbalancing two apache server then u can have http redirect rules at apache level.

Thank you..

 

Red- I want a web application with a conetxr root (for eg: items) get load balanced between two servers.

Blue/red-- any example please, how rule works..  is it like URI with so and so hostname and conetxt root, then  those  requests will be redirected to these list of servers  defined at LB level ( depending on algorithm) 

[micxas]

remember one thing only network guys should use the term "VIP" , for all other like middleware admins, developers etc...its just ip. the term vip will confuse you.

Yeah I was confused at first, my manager explained me saying it's just a hostname with an Ip address..:) Thanks man.

[micxas]

pool members- Backend servers  ee kada ?

Algorithm- Yeah got it.

Then where is  the concept of context root coming into picture man? I am aware tht its there at backend servers level, but at load balancer level ?

Scrooge man Thank you  %$#$

[micxas]

Round robin DNS & DDNS (Dynamic DNS) is often used to load balance requests between a number of Web servers. For example, a company has one domain name and three identical copies of the same web site residing on three servers with three different IP addresses. When one user accesses the home page it will be sent to the first IP address. The second user who accesses the home page will be sent to the next IP address, and the third user will be sent to the third IP address. In each case, once the IP address is given out, it goes to the end of the list. The fourth user, therefore, will be sent to the first IP address, and so forth

Great, but mari simple ga telchesadu, konchem depth ga expecting :) Appreciate man, thank you.. 

[k2s]

Thank you..
 
Red- I want a web application with a conetxr root (for eg: items) get load balanced between two servers.
Blue/red-- any example please, how rule works..  is it like URI with so and so hostname and conetxt root, then  those  requests will be redirected to these list of servers  defined at LB level ( depending on algorithm)

write an irule to match "items" in Uri when connection established

[maverick23]

in wat is context root??...brief explanation plss

[maverick23]

Between I am interested in learning middleware concepts...any docs or videos to get going...romba nandri

[pythonic]

in wat is context root??...brief explanation plss

 

Nee resquests ela dispatch cheyali ani like aa app or view or servlets ki foward cheyali ani define cheyathaniki context root use avvudhi man....

 

Same way for all POST, PUT etc....so this is just regex matching and forwarding to relevant view....