Sending Excess Load To the Cloud?

TristanBrotherton writes "Cloud computing seems to be a good choice for startups like ours, looking to scale easily with users. (We're providing a series of Web services, assets, and Web applications to users of our mobile client.) There are the obvious choices of Google, Amazon, and smaller shops like EngineYard. The biggest issue we have in choosing cloud computing to run our applications is trust in their robustness. If the provider goes down, we suffer. In traditional hosting environments we mitigate this with multiple sites / vendors. It's not really feasible to host on multiple compute services, so I wondered if a better option might be to set up a small (perhaps two servers) origin infrastructure in a traditional manner at a datacenter, running our applications, but then send excess load, or in the event of our origin servers failing, all load, to compute services. This would give us the best of both worlds. Has anyone done this, or had experience in designing Web applications to scale seamlessly across both environments? Is there particular load-balancing hardware we can use to do this?"

Comments

The C word

[jaxtherat]

Please don't use it. Every time you use a buzz-phrase God kills a kitten.

Re:The C word

[MrNaz]

It's a term invented by idiot managers who saw all those diagrams where the wider internet is represented by a picture of a cloud and were too stupid to grasp the concept of a representative diagram, so they took the picture of the cloud to be literal, and now there is an entire generation of managers who have an image of electrons flying around the sky. They confusion they suffer is only exacerbated when there's a thunderstorm and they hear the word "torrent" to describe the rain, thinking that the storm is the result of those damned P2P users.

Re:Cloud is over-rated...

[RuBLed]

"jack of all trades, mater of none"

yup, im in slashdot alright...