Here's my take on these features... Monitoring and autoscaling I'll pass on. You can get better monitoring with collectd for free and autoscaling based on just load age or disk util and not app specific stuff is plain crazy. The load balancer is pretty nice but I'll stick with haproxy until you can do httpand https on the same lb and also currently you can only do CNAME dns so no foo.com only www.foo.com and wildcard…
Amazon EC2 gets statistics, auto scaling and elastic load balancing
41–44 of 44 posts
I guess I spoke too soon and they did add support for multiple ports through the sam lb access point. So http and https can be served from the same lb. This makes the lb much more interesting.
Re: Amazon EC2 gets statistics, auto scaling and elastic load balancing
#42Re: Amazon EC2 gets statistics, auto scaling and elastic load balancing
#43In the case of websites, auto scaling is useful only if your application is not too dependent on DB but most web apps have DB as the bottle neck. The way auto scaling works is to launch new instances but that works only for application servers. You can't autoscale a DB by launching new instances. So, even though this feature is useful it is not taking away the biggest headache in website scaling..i.e how to scale you…
Does anything prohibit someone from hacking together a way to scale their DB using this service? i.e. fire up instances that of a certain ilk? Not sure how detailed CloudWatch is, but you could conceivably automate anything that involves looking at numbers and taking steps to reduce load on your DB.
Hum, funny you say that, that's exactly what I'm working on: http://code.google.com/p/hotrepart/ The idea is to repartition a DB across multiple hosts while it's running. It's only a demonstrator project right now.
Re: Amazon EC2 gets statistics, auto scaling and elastic load balancing
#44really sad that they only provide a cname and you can;t associate Elastic IP to it. You can;t point it to your root domain....