它已经上牌了一段时间，但现在，亚马逊已经发布了弹性负载均衡（ ELB），你有什么想法上部署该解决方案的高流量网络应用程序？

It's been on the cards for a while, but now that Amazon have released Elastic Load balancing (ELB), what are your thoughts on deploying this solution for a high-traffic web application?

我们是否应该更换 HAProxy的或考虑ELB作为一个免费的服务HAProxy的面前？

Should we replace HAProxy or consider ELB as a complimentary service in front of HAProxy?

推荐答案

我一直在运行的ELB，而不是HAProxy的约一个月，现在一个网站，得到平均每天约10万人次​​，而我一直pretty的满意的结果。

I've been running an ELB instead of HAProxy for about a month now on a site that gets about 100,000 visits per day, and I've been pretty pleased with the results.

一个疑难杂症，但（更新，此问题已得到修复亚马逊AWS ，见下面的评论）：

A gotcha though (UPDATE, this issue has been fixed by Amazon AWS, see comments below):

您不能加载平衡域的根，你必须创建一个 CNAME 别名负载平衡器。一旦解决方案是从 http://mysite.com 所有流量重定向到 http://www.mysite.com 。 You can't load balance the root of a domain as you have to create a CNAME alias to your load balancer. Once solution is to redirect all traffic from http://mysite.com to http://www.mysite.com.

除此之外，我真的不能说高度不够的AWS ELB产品的。我还使用了CloudWatch的监控和自动缩放。哦，不要忘记它是$ 0.10比运行一个小的 EC2实例（$ 0.025每小时更便宜的替代）。

Apart from that I really can't speak highly enough of the AWS ELB offerings. I'm also using the Cloudwatch monitoring and autoscaling. Oh and don't forget it's cheaper than running a small EC2 instance ($0.025 per hour instead of $0.10).