3 ms·

How much headroom do the 'cloud' providers allow? Presumably any sudden, broad, increase in demand for servers is going to cause problems if there are no physi

How much headroom do the 'cloud' providers allow? Presumably any sudden, broad, increase in demand for servers is going to cause problems if there are no physical machines to support the instances - however many times you scribble the word 'Cloud' on your design in crayon.

TrevorJ 17y ago
One would hope that scalable architecture is one of the main selling points of cloud computing.
- wglb 17y ago
  So how long does it take to power up amazon instances in the case of a news item like this? Or do you have to have them standing by already allocated? If so, isn't it cheaper to build you own?
  - bmelton 17y ago
    Ways I've found that work for pretty quick scaling on EC2 (YMMV, and I'm not that smart or seasoned on it, so don't take this as canon.) You need to have the elastic block storage (or some remotely mountable storage you trust to be up). On this storage, you put things like your database and other dynamic content that you expect to persist through a reboot of the box, which reverts back to its base image. You need to configure a couple of boxes at least, one to act as a load balancer, and another to act as the content provider. For more laden sites than mine, you might also need a separate instance for just the DB. You are going to eat the cost of static IPs for at least a few boxes, but that's pretty cheap. Configure those IPs to be in your load balancer always. They'll fail when they're down, but that shouldn't be an issue. At this point, you can have basically as many boxes available as you have previously allocated, and bringing them online is as simple as turning them on. You could probably use CloudKick to dynamically bring them online, but I haven't really played with it to know. If you need scaling past that allocation, you can bring up more instances (the bottleneck will of course be the DB), and register them with the load balancer as you need.

TrevorJ 17y ago

One would hope that scalable architecture is one of the main selling points of cloud computing.

wglb 17y ago
So how long does it take to power up amazon instances in the case of a news item like this? Or do you have to have them standing by already allocated? If so, isn't it cheaper to build you own?
- bmelton 17y ago
  Ways I've found that work for pretty quick scaling on EC2 (YMMV, and I'm not that smart or seasoned on it, so don't take this as canon.) You need to have the elastic block storage (or some remotely mountable storage you trust to be up). On this storage, you put things like your database and other dynamic content that you expect to persist through a reboot of the box, which reverts back to its base image. You need to configure a couple of boxes at least, one to act as a load balancer, and another to act as the content provider. For more laden sites than mine, you might also need a separate instance for just the DB. You are going to eat the cost of static IPs for at least a few boxes, but that's pretty cheap. Configure those IPs to be in your load balancer always. They'll fail when they're down, but that shouldn't be an issue. At this point, you can have basically as many boxes available as you have previously allocated, and bringing them online is as simple as turning them on. You could probably use CloudKick to dynamically bring them online, but I haven't really played with it to know. If you need scaling past that allocation, you can bring up more instances (the bottleneck will of course be the DB), and register them with the load balancer as you need.