More cloud computing thoughts
Further to my recent comments about cloud computing – I am currently helping a new site set itself up – we want to use a traditional hosting service but with the option of dynamically expanding into the cloud if bandwidth or other capacity limits are approached. Somebody had a bright idea – set up a free starter account a goggrid, configure a loadbalancer as the public address of the site and point the loadbalancer back at our server. Then when we need to we can start up a gogrid server and have the loadbalancer distribute load between the two servers. Brilliant – just the kind of scenario I wrote about, and a logical use of cloud capacity. Unfortunately gogrid don’t let you configure a loadbalancer to point to anything but their own servers. Rats. Something is going to have to give here if this concept is ever going to take flight.
Tags: cloud computing
Check out Dynect (dynect.com) – it provides DNS management and routing tools that allow you to manage all this stuff. It’s an extra layer, but it’s specifically designed for this sort of use case. And I wouldn’t put a connection over the public behind a load balancer, that would introduce all sorts of reliability and latency issues.
Hi – thanks for that, yes it does look interesting. I think this is an important piece of the jigsaw puzzle. I’ll check it out and report back on my findings.