What the Cloud IS and IS NOT

Tracey Flanders Published Jul 29, 2014 at 5:13 PM MST by Tracey Flanders Tags Cloud, DevOps  Leave comment

Using the cloud will require habitual changes in the way IT resources are consumed. The traditional IT way of deploying applications is not a recommended method to place an enterprise into the cloud. Long term the costs will exceed the benefits.

 

 

Absolute application automation is required to reap the benefits of any cloud provider. Over sizing hardware resources can lead to idle cloud resources, unnecessary hourly charges would apply. AWS best practices suggest using only what you need and tear down what you don’t. Methods such as auto-scaling, latency based DNS load balancing, and multiple instances type will allow for any enterprise application to have elasticity and the flexibility needed. There are many reporting tools that can help with cloud resource waste.


A DevOps team within IT would be needed to close the gaps between Operations and Development. These individuals would be automation SME’s with infrastructure, performance tuning and programming experience. Tools such as Puppet, Chef and scripting to AWS APIs with Linux BASH or Windows PowerShell would be the preferred methods for cloud automation.


Solutions such as VMware vCAC (Cloud Automation Center) could be deployed to encapsulate the multiple IaaS clouds under a single self-service portal to allow for better integration with existing private clouds.

 

 

WHAT THE CLOUD IS

A place to:

   * Fail faster and waste less money and resources.

   * Be agile with application development.
   * Get an edge on the competition with faster time to market without months of infrastructure deployment
   * Automatically scale your applications during peeks customer usage and downscale in off peak hours.
   * Launch large scale jobs for a short time with minimal investment
   * Archiving large regulated datasets that can expire after x time.

 


AND WHAT THE CLOUD IS NOT


A place to:

   * Deploy traditional applications that are not cloud aware.

   * Leave idle hardware resources.

   * Circumvent IT infrastructure and Security rules and regulations.
   * Perform manual steps in order to keep applications running.
   * Just for startups.
   * A fad that will go away.





Leave comment

We welcome your participation on our website. Please keep your comments civil and on point. Your email address may be used to notify you of comment replies.
By submitting a comment, you agree to these Terms of Use.


Login to comment on this article.