Traditional Infrastructure Capacity Models vs. Cloud Capacity Models

Traditional Capacity Models vs. Cloud Capacity Models

Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time

Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion:

Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion: • Large CAPEX due to hardware investment

Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion: • Large CAPEX due to hardware investment • Financing overcapacity

Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion: • Large CAPEX due to hardware investment • Financing overcapacity • Customer dissatisfaction when actual demand outperforms available capacity

Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time

Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion:

Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion: • No investment in hardware; from CAPEX to OPEX

Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion: • No investment in hardware; from CAPEX to OPEX • No nancing of overcapacity

Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion: • No investment in hardware; from CAPEX to OPEX • No nancing of overcapacity • Customer satisfaction because capacity automatically scales to meet actual demand

Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand

Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand Conclusion:

Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand Conclusion: • Large CAPEX to meet actual demand peak

Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand Conclusion: • Large CAPEX to meet actual demand peak • Financing overcapacity between batch processes

Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity

Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion:

Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion: • No CAPEX, only operational expenditure

Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion: • No CAPEX, only operational expenditure • No need to nance overcapacity between batch processes

Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion: • No CAPEX, only operational expenditure • No need to nance overcapacity between batch processes • Capacity automatically available when needed

Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time

Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion:

Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • Large capital expenditure due to unpredictable demand of campaigns

Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • Large capital expenditure due to unpredictable demand of campaigns • Inef cient use of available capacity for campaigns

Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • Large capital expenditure due to unpredictable demand of campaigns • Inef cient use of available capacity for campaigns • Customer dissatisfaction when campaign becomes too successful

Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time

Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion:

Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • No need to invest in hardware

Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • No need to invest in hardware • Ef cient use of capacity, since it automatically scales per campaign

Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion: • No need to invest in hardware • Ef cient use of capacity, since it automatically scales per campaign • Campaigns are always available, even when very successful

Why Jitscale?

Why Jitscale? Cloud over cloud infrastructure

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds.

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management Your infrastructure is made available only when necessary, on an hourly basis. Jitscale also manages all technical aspects of your application and platform pro-actively, 24/7, 365 days a year, anywhere in the world.

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management Your infrastructure is made available only when necessary, on an hourly basis. Jitscale also manages all technical aspects of your application and platform pro-actively, 24/7, 365 days a year, anywhere in the world. Service level agreement

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management Your infrastructure is made available only when necessary, on an hourly basis. Jitscale also manages all technical aspects of your application and platform pro-actively, 24/7, 365 days a year, anywhere in the world. Service level agreement The entire service provided by Jitscale will be detailed in a comprehensive SLA.

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management Your infrastructure is made available only when necessary, on an hourly basis. Jitscale also manages all technical aspects of your application and platform pro-actively, 24/7, 365 days a year, anywhere in the world. Service level agreement The entire service provided by Jitscale will be detailed in a comprehensive SLA. Pay per success

Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management Your infrastructure is made available only when necessary, on an hourly basis. Jitscale also manages all technical aspects of your application and platform pro-actively, 24/7, 365 days a year, anywhere in the world. Service level agreement The entire service provided by Jitscale will be detailed in a comprehensive SLA. Pay per success You only invest in server capacity and management that is actually used and can cut costs by 75% compared to traditional infrastructures.

Jitscale provides fully managed, on demand, global, auto-scaling, virtualized and shared IT infrastructure as-a-service. For more information, please visit our website: www.jitscale.com

http://www.jitscale.com	83
http://www.slideshare.net	15
http://www.arjandejong.nl	1

Traditional Infrastructure Capacity Models vs. Cloud Capacity Models

by Jitscale on Apr 02, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

3 Embeds 99

Statistics

Traditional Infrastructure Capacity Models vs. Cloud Capacity Models — Presentation Transcript