We generally tell people either use DNS load balancing or put a Software or HW load balancing
1. DNS load balancing is low 2. S/W load balancing does not scale up (new some other load balancer in front) 3. HW load balancing is expensive Seem there is 4th choice, that is use TCP IP routing. Basically, you can setup router to forward requests to multiple nodes when it see packets to specific IP. Above can mess up sessions, so this is used with hash based routing to get router to send all packets from same source IP to one machine. I could not find a good description about this, but this linkedin tech talk discuss it for few minutes http://www.youtube.com/watch?v=2WuT2rdLK5A -- ============================ Srinath Perera, Ph.D. Director, Research, WSO2 Inc. Visiting Faculty, University of Moratuwa Member, Apache Software Foundation Research Scientist, Lanka Software Foundation Blog: http://srinathsview.blogspot.com/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
