Submission + - How to handle flash crowds from your garage
slashdotmsiriv writes: For years, developers and researchers have been refining way to scale Internet services to larger and larger capacities. However, racks full of web servers, database replicas, and load balancing switches require a significant up-front investment. For popular sites, where load is consistently high, it is easy to justify this investment; the resources will not be idle. Less popular sites can not justify the expense of large idle capacity.
The burning question is how can a low-traffic garage-innovator site make the transition to high-traffic when the slashdot hordes make that transition without warning?
This article describes the issues and tradeoffs a typical garage innovator encounters when building low-cost, scalable Internet services. This is a more formal analysis of the problem and solutions discussed here regarding Animoto's sudden need to scale-up. In addition, the article offers an overview of current state of utility computing (S3, EC2 etc) and of the most common strategies for building scalable Internet services.
Seems that utility computing is the way of the future for scalable network services; it would be nice to know how to make best use of it.
This article describes the issues and tradeoffs a typical garage innovator encounters when building low-cost, scalable Internet services. This is a more formal analysis of the problem and solutions discussed here regarding Animoto's sudden need to scale-up. In addition, the article offers an overview of current state of utility computing (S3, EC2 etc) and of the most common strategies for building scalable Internet services.
Seems that utility computing is the way of the future for scalable network services; it would be nice to know how to make best use of it.
