To continue our series on Cloud Application Chalk Talks, our "chief geek" John will cover Development and Test Clouds. After the move toward commoditizing some hardware and capacity in Public clouds, we find that the next logical step is using Clouds to level off Pre-Production costs throughout the software lifecycle.
Capacity in Production is fairly easy to predict, but it is hard to predict in Pre-production. You can plan to make capacity for spikes and volume and provision your infrastructure if you are an eCommerce vendor getting ready for the next Christmas rush. But what if you could eliminate 80% of the unpredictability of the Pre-Production environment that hundreds of skilled developers and testers use, and therefore not need to buy all that capacity up front? Private/Public Clouds are a great way for our partners to pool together computing resources into Private Clouds, use Public Clouds for overages, and try to regulate their infrastructure costs (compare oh, $.06-.12 a CPU hour of private/public capacity vs. $2.00 for each team using dedicated systems - and you see the economics).
So what happens next? We'll cover how companies are dealing with those "spikes" in capacity and cost, as well as the hidden costs that you don't usually hear about in the standard arguments for employing Cloud Computing and Virtualization in pre-production.
Capacity in Production is fairly easy to predict, but it is hard to predict in Pre-production. You can plan to make capacity for spikes and volume and provision your infrastructure if you are an eCommerce vendor getting ready for the next Christmas rush. But what if you could eliminate 80% of the unpredictability of the Pre-Production environment that hundreds of skilled developers and testers use, and therefore not need to buy all that capacity up front? Private/Public Clouds are a great way for our partners to pool together computing resources into Private Clouds, use Public Clouds for overages, and try to regulate their infrastructure costs (compare oh, $.06-.12 a CPU hour of private/public capacity vs. $2.00 for each team using dedicated systems - and you see the economics).
So what happens next? We'll cover how companies are dealing with those "spikes" in capacity and cost, as well as the hidden costs that you don't usually hear about in the standard arguments for employing Cloud Computing and Virtualization in pre-production.
Comments