load balancing - ELB on Amazon - is it "worth it" in this case? -
we're thinking moving elastic load balancer on amazon. however, turns out since use more 1 domain name, have rename of our applications limit single elb. issue use free level 1 certificates, whereas moving elb require moving level 2, although that's not huge deal. issue don't have lot of volume @ point, , don't have need load-balancing in terms of traffic alleviation. also, in case of failure of amazon instance, seems quite rare (have not experienced in several years), can , running creating instance , restoring.
otoh, according read it, people happy , recommend it, due ease of setup , value brings.
given above, worth it?
since use more 1 domain name, have rename of our applications limit single elb
what makes this? there's nothing preventing launching multiple elb's if want to. , if application manages multiple domains there's no reason single elb can't handle either. have 1 elb fronting application on bunch of ec2 instances 11 different domains point to.
another issue use free level 1 certificates, whereas moving elb require moving level 2, although that's not huge deal.
not sure mean "level one" , "level 2". if you're using self-signed ssl certificate you'll need switch using certificate signed third party certificate authority, indeed cost money. amazon supports manner of certificates, including simple certs, ev certs, san certs, etc. you'll find more information on elb , ssl certs in aws documentation.
also, in case of failure of amazon instance, seems quite rare (have not experienced in several years), can , running creating instance , restoring.
consider lucky. we've had amazon instances fail time time, , regularly notifications amazon instances need rebooted in order migrate them off of faulty/old hardware.
if don't care being down while , feel don't need capacity load balancer , multiple appservers provides there's no reason move using elb. if want reliability of multiple appservers moving elb indeed idea.
and if anticipate traffic level growing might want consider using amazon's auto scaling tools. using auto scaling tell amazon minimum number of application servers want running behind elb, , parameters indicate when should automatically launch additional instances if/when load increases.
our amazon account rep recommended if had single instance wanted minimize downtime of (like monitoring server, etc) should create auto scaling group limit of 1 instance in it. way if instance ever die reason whatsoever, amazon automatically spin new replacement instance.
Comments
Post a Comment