News
1/9/2013
00:00 AM
Bill Kleyman
Bill Kleyman
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

When Cloud Computing Is The Wrong Fit

ROI is the first question to answer when deciding if cloud computing is a good platform for your enterprise. Three others involve compliance, infrastructure, and a strong business case.

I’m a big fan of cloud computing and always enjoy seeing it done right. This means good planning, a solid infrastructure, and a use-case that directly fits what the cloud can deliver.

Today, almost every organization that uses the Internet is utilizing some element of cloud computing. The differentiator is the cloud model and the extent to which that model is deployed. In my experience there are instances where a particular cloud platform is a great fit. On the other hand, some companies absolutely do not need this type of solution.

One of the most important first steps to take when you are deciding whether or not to adopt a cloud platform is to establish a solid use-case that can generate ROI. From there, you should look at the investment your company will need to make. In some cases, migrating to the cloud just won’t make sense. Here are three examples.

1. Compliance and regulations
Unless you are planning a very secure private cloud solution, many cloud computing platforms will leverage some element of a public Internet infrastructure. This might mean sharing bandwidth or utilizing a datacenter to host your solution.

Think twice about the cloud if you’re in an industry heavily monitored by compliance rules and regulations. Only a handful of enterprise datacenters are able to manage PCI compliance for organizations that use them as hosts. Also, PCI compliance may come at a high cost. Remember to always take regulations into account prior to committing to a cloud provider.

2. Infrastructure
In some cases, the business plan is there, but the environment is not. A good cloud solution often means using pieces from storage, LAN/WAN, servers, virtualization, user control, and putting them all together. If some part isn’t there or something isn’t ready to handle this type of new load, there’s a good chance you’ll experience some performance degradation.

This situation is where analyzing ROI and the actual business investment is critical. Be sure to ask key questions like how much additional hardware will you need to buy and whether it actually makes sense to host infrastructure off site. What’s more, having infrastructure doesn’t only limit you to hardware. You also have to have the right people to support your cloud environment. This means employing engineers who are cloud-ready and managers who understand the vision of their cloud model.

3. Poor business-case
Developing a strong business case means identifying a set of challenges and finding a way to overcome problems with an intelligent piece of technology. Unfortunately, unexpected events can slow down the cloud migration process and cost companies a lot of money.

To avoid a cloud budget-buster, it’s important to develop a business-case that utilizes technology that will perform for current and future needs. That means that datacenter managers and architects have to consider how their business will evolve and be flexible and forward-thinking in developing a cloud strategy. For example, if administrators provision hardware that can’t support users after a year or so, it’s quite possible that the initial planning was flawed, and the results will be disastrous.

Like any technology, cloud computing starts with a well-conceived plan and an infrastructure that will endure. Processes like testing, maintenance, business continuity, and even personnel training are all very important to weigh when considering the pluses and minuses of migrating to the cloud. With the right model in place and a good infrastructure, the cloud can be a powerful platform to leverage. However, with the wrong mindset and a poorly planned deployment, a cloud model can quickly become a cash-drain.

This article originally appeared in The Transformed Datacenter on 1/9/2013.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
DevOps’ Impact on Application Security
DevOps’ Impact on Application Security
Managing the interdependency between software and infrastructure is a thorny challenge. Often, it’s a “developers are from Mars, systems engineers are from Venus” situation.
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4262
Published: 2014-07-28
svnwcsub.py in Subversion 1.8.0 before 1.8.3, when using the --pidfile option and running in foreground mode, allows local users to gain privileges via a symlink attack on the pid file. NOTE: this issue was SPLIT due to different affected versions (ADT3). The irkerbridge.py issue is covered by CVE-...

CVE-2013-4840
Published: 2014-07-28
Unspecified vulnerability in HP and H3C VPN Firewall Module products SECPATH1000FE before 5.20.R3177 and SECBLADEFW before 5.20.R3177 allows remote attackers to cause a denial of service via unknown vectors.

CVE-2013-7393
Published: 2014-07-28
The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created for (1) svnwcsub.py or (2) irkerbridge.py when the --pidfile option is used. NOTE: this issue was SPLIT from CVE-2013-4262 based on different affected versions...

CVE-2014-2974
Published: 2014-07-28
Cross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through 6.2.4 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts.

CVE-2014-2975
Published: 2014-07-28
Cross-site scripting (XSS) vulnerability in php/user_account.php in Silver Peak VX before 6.2.4 allows remote attackers to inject arbitrary web script or HTML via the user_id parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.