Traditional Infrastructure Capacity Models vs. Cloud Capacity Models

4,264 views

Published on

The presentation compares traditional infrastructure capacity models to cloud capacity models.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,264
On SlideShare
0
From Embeds
0
Number of Embeds
241
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

































  • Traditional Infrastructure Capacity Models vs. Cloud Capacity Models

    1. 1. Traditional Capacity Models vs. Cloud Capacity Models
    2. 2. Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time
    3. 3. Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion:
    4. 4. Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion: • Large CAPEX due to hardware investment
    5. 5. Infrastructure Costs Traditional Infrastructure Capacity Model Estimated Demand Hardware Demand Actual Demand Time Conclusion: • Large CAPEX due to hardware investment • Financing overcapacity
    6. 6. 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
    7. 7. Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time
    8. 8. Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion:
    9. 9. Infrastructure Costs Jitscale Infrastructure Capacity Model Estimated Demand Jitscale Capacity Actual Demand Time Conclusion: • No investment in hardware; from CAPEX to OPEX
    10. 10. 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
    11. 11. 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
    12. 12. Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand
    13. 13. Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand Conclusion:
    14. 14. Traditional Batch Processing Capacity Model Infrastructure Costs Time Hardware Demand Actual Demand Conclusion: • Large CAPEX to meet actual demand peak
    15. 15. 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
    16. 16. Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity
    17. 17. Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion:
    18. 18. Jitscale Batch Processing Capacity Model Infrastructure Costs Time Actual Demand Jitscale Capacity Conclusion: • No CAPEX, only operational expenditure
    19. 19. 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
    20. 20. 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
    21. 21. Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time
    22. 22. Traditional Campaign Capacity Model Infrastructure Costs Estimated Demand Hardware Demand Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion:
    23. 23. 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
    24. 24. 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
    25. 25. 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
    26. 26. Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time
    27. 27. Jitscale Campaign Capacity Model Infrastructure Costs Estimated Demand Jitscale Capacity Actual Demand Campaign 1 Actual Demand Campaign 2 Time Conclusion:
    28. 28. 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
    29. 29. 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
    30. 30. 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
    31. 31. Why Jitscale?
    32. 32. Why Jitscale? Cloud over cloud infrastructure
    33. 33. Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds.
    34. 34. Why Jitscale? Cloud over cloud infrastructure Your data can be diffused over multiple clouds. Auto-scaling infrastructure and management
    35. 35. 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.
    36. 36. 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
    37. 37. 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.
    38. 38. 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
    39. 39. 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.
    40. 40. 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

    ×