Agile Testing: Load Balancing in Amazon EC2 with HAProxy
o3 magazine | Open Source SSL Acceleration
A look at utilizing Open Source projects to build an SSL Accelerator for Web Servers that rivals even the most expensive commercial solutions. Advanced SSL Acceleration, Layer 7 URL Processing and Web Acceleration through gzip off-loading.Using Nginx as a load balancer
Configuring nginx as load balancer
NginxAWS Elastic Load Balancer Tutorial | Lead Thinking
protocol=http, lb-port=80, instance-port=80
http://leadthinking.com/42-aws-elastic-load-balancer-tutorial http://docs.amazonwebservices.com/ElasticLoadBalancing/latest/DeveloperGuide/ http://elwoodicious.com/2009/11/23/ec2-elastic-load-balancing-for-fun-and-profit/ http://af-design.com/blog/2009/07/15/3-amazon-elastic-load-balancer-tips/ http://ajohnstone.com/archives/ec2-tools-installation-ami-api-elastic-load-balancing-elb-and-cloud-watch/ http://topsy.com/tb/leadthinking.com/42-aws-elastic-load-balancer-tutorial http://lixconsulting.blogspot.com/2009/10/aws-setup-load-balancer.html http://docs.amazonwebservices.com/ElasticLoadBalancing/2009-05-15/DeveloperGuide/
adding elb to amazon servers
You can load balance your Mysql cluster – however ELB is outside Amazon’s firewall and isn’t integrated with it. This means that to load balance Mysql you need to open it up to the world and rely on strong credentials to keep your data secure, rather than firewall rules.
We’ve been using the new Amazon Load Balancers (ELB) for Socialmod, and since there’s not much information out there on the subject, I thought a blog post would be in order.High-Performance DNS for The Cloud - igvita.com
DNS is a great example of a service that couldn't possibly work on paper, but performs spectacularly in practice, even with a hodge-podge of implementations all over the Internet.
DNS is a great example of a service that couldn't possibly work on paper, but performs spectacularly in practice, even with a hodge-podge of implementations all over the Internet. First, the authoritative DNS servers responds with a Time To Live (TTL) timestamp for every record (which you should keep fairly low in a virtual deployment environment), then the upstream DNS servers cache that same data, albeit usually with different policies (determined by the ISP). And finally, your router, OS, and the browser all have their own and independent DNS caches. (Firefox 2/3 caches all DNS records for a 1 minute, IE 5/6/7 for 15 minutes). Talk about a mess!
Good tips on using DNS in the cloud, and in particular using a staging environment that is switched over (via DNS) to a production environment.