| By Srinivasan Sundara Rajan | Article Rating: |
|
| November 29, 2010 05:00 AM EST | Reads: |
7,524 |
Dynamic Scaling
A key benefit of cloud computing is the ability to add and remove capacity as and when it is required. This is often referred to as elastic scale. Being able to add and remove this capacity can dramatically reduce the total cost of ownership for certain types of applications; indeed, for some applications cloud computing is the only economically feasible solution to the problem.
This particular property will be the most valued to evaluate a cloud platform, and I have provided a comparison between two of the major IaaS platforms:
- Amazon EC2
- Windows Azure (Which is also a PaaS on top of the IaaS Offering)
Amazon EC2
Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers.
Amazon EC2 provides out-of-the-box support for elasticity and auto scaling with multiple components.
Amazon CloudWatch
Amazon CloudWatch is a web service that provides monitoring for AWS cloud resources, starting with Amazon EC2. It provides visibility into resource utilization, operational performance, and overall demand patterns - including metrics such as CPU utilization, disk reads and writes, and network traffic.
Auto Scaling
Auto scaling allows you to automatically scale your Amazon EC2 capacity up or down according to conditions you define. With auto scaling, you can ensure that the number of Amazon EC2 instances you're using scales up seamlessly during demand spikes to maintain performance, and scales down automatically during demand lulls to minimize costs. Auto scaling is particularly well suited for applications that experience hourly, daily, or weekly variability in usage. Auto scaling is enabled by Amazon CloudWatch and available at no additional charge beyond Amazon CloudWatch fees.
Auto scaling utilizes the following concepts.
- An AutoScalingGroup is a representation of an application running on multiple Amazon Elastic Compute Cloud (EC2) instances.
- A Launch Configuration captures the parameters necessary to create new EC2 Instances. Only one launch configuration can be attached to an AutoScalingGroup at a time.
- In Auto Scaling, the trigger mechanism uses defined metrics and thresholds to initiate scaling of AutoScalingGroups.
The following diagram, courtesy of Amazon EC2 site, gives the over view of auto scaling in Amazon EC2.

Windows Azure
The Windows Azure platform consists of the Windows Azure cloud-based operating system, which provides the core compute and storage capabilities required by cloud-based applications as well as some constituent services - specifically the service bus and access control - that provide other key connectivity and security-related features.
Windows Azure also provides robust dynamic scaling capabilities, however there are no named products like EC2 but rather a custom-coding approach is used at this time. However, there are third-party providers that are in the process of developing dynamic scaling applications.
In Windows Azure, auto scaling is achieved by changing the instance count in the service configuration. Increasing the instance count will cause Windows Azure to start new instances; decreasing the instance count will in turn cause it to shut instances down.
Decisions around when to scale and by how much will be driven by some set of rules. Whether these are implicit and codified in some system or simply stored in the head of a systems engineer, they are rules nonetheless.
Rules for scaling a Windows Azure application will typically take one of two forms. The first is a rule that specifies to add or remove capacity from the system at a given time - for example: run 20 instances between 8 am and 10 am each day and two instances at all other times. The second form is rules that are based around a response to metrics and this form warrants more discussion.
Taking action to scale Windows Azure is exposed through the use of the management API. Through a call to this API it is possible to change the instance count in the service configuration and in doing so to change the number of running instances.
Summary
Auto scaling is the number one feature in a cloud platform that directly addresses the need to reduce cost for large enterprises.
Both EC2 and Azure provide the auto scaling feature. While EC2 provides a backbone and framework for auto scaling, Azure provides an API that can be extended. Already we are seeing several third-party providers delivering tools for Azure auto scaling.
Published November 29, 2010 Reads 7,524
Copyright © 2010 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Srinivasan Sundara Rajan
Srinivasan Sundara Rajan works at Gavs Technologies as a Chief Architect. His primary focus is enabling Agile Enterprises by facilitating the adoption of Every Thing As A Service Model with particular concentration on BpaaS (Business Process As A Service). Srinivasan is currently writing a series of articles on Indutry SaaS/BpaaS use cases which enterprises can adopt.All the views expressed are Srinivasan's independent analysis of industry and solutions and need not necessarily be of his current or past organizations. Srinivasan would like to thank every one who augmented his Architectural skills with Analytical ideas.
- Ubuntu-based Open Source Linux Mint Tests KDE Version
- NetArt Chooses Open-Xchange to Enter into Cloud Application Business
- Rackspace Starts the Great OpenStack Migration
- Cloud Expo: Architect Full Performance Potential of IaaS Cloud Services
- Hot Tech Firms at the 2012 DoDIIS Conference
- Dell and Morphlabs Partner on SSD Cloud
- Microsoft Sets Up an Open Source Subsidiary
- Piston to Integrate Cloud Foundry & OpenStack
- Dell Buys Mainframe Modernizer in Cloud Push
- Informatica Upgrades Its iPaaS
- Inktank to Commercialize Ceph Big Storage
- Video Streaming Outside The Firewall Market Shares, Strategies, and Forecasts, Worldwide, 2012 to 2018
- Red Hat Executive Appointed to Technology Services Industry Association (TSIA) Support Services Advisory Board
- Ubuntu-based Open Source Linux Mint Tests KDE Version
- What Kind of Software Company Should You Work For?
- NetArt Chooses Open-Xchange to Enter into Cloud Application Business
- Rackspace Starts the Great OpenStack Migration
- TeamDrive 3.0 Unveiled at CeBIT: Brings Enterprise-Grade Security to Cloud File Sharing on the iPhone, iPad and Android
- Cloud Expo: Architect Full Performance Potential of IaaS Cloud Services
- Sorting Through the APM Clutter
- Hot Tech Firms at the 2012 DoDIIS Conference
- Swisscom Floats Red Hat Cloud
- Dell and Morphlabs Partner on SSD Cloud
- Microsoft Sets Up an Open Source Subsidiary
- The i-Technology Right Stuff
- Linux.SYS-CON.com Exclusive: Linus Discloses *Real* Fathers of Linux
- After Ubuntu, Windows Looks Increasingly Bad, Increasingly Archaic, Increasingly Unfriendly
- A Closer Look at Damn Small Linux
- Linus' Top Ten SCO Barbs
- SCO CEO Posts Open Letter to the Open Source Community
- Netscape Co-Founder's 12 Reasons for Growth of Open Source
- Where Are RIA Technologies Headed in 2008?
- *POINT - COUNTERPOINT SPECIAL* What's Wrong with the Open Source Community?
- Introducing "Cooperative Linux" - Linux for Windows, No Less
- Linux.SYS-CON.com Exclusive: What Would UserLinux Look Like?
- Why Recovering a Deleted Ext3 File Is Difficult . . .




















