4 ms·

I'm curious, what stuff are you talking about? Admittedly, ELB's cname restriction is a little of a downer but you could always spin up an instance to act as yo

by ambirex 16y ago

I'm curious, what stuff are you talking about? Admittedly, ELB's cname restriction is a little of a downer but you could always spin up an instance to act as your own LB. Also, their 3rd point of needing to rebuild an ELB is a little of a drag but it is very trivial to rebuild by hand, even faster if you have scripted it.

wlll 16y ago
Moving EC2 elastic IPs can take a while in my experience, and also time for creating servers can be unpredictable. With the BrightBox stuff "Load Balancers are normally created and handling traffic within 90 seconds.", also the video here http://blog.brightbox.co.uk/posts/announcing-brightbox-cloud-the-uks-first-true-iaas-platform http://blog.brightbox.co.uk/posts/announcing-brightbox-cloud... seems to show server booting and ip assigning as pretty snappy. If they can maintain this responsiveness in the face of lots of production usage then it would be a good selling point.
oceanician 16y ago
"but it is very trivial to rebuild by hand, even faster if you have scripted it" trouble is, anything that is trivial by hand for you, after you've done it 20 times is tricky for Sys Admins to pick up. And if you script it, when an automated solution is already available, you could be using that time to build business logic, which I'm guessing the main point of most people's role here?