Two key reasons deploying to the cloud is different


Become An Insider

Sign up now and get free access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content from the best tech brands on the Internet: CIO, CSO, Computerworld, InfoWorld, IT World and Network World Learn more.

Visualizing a cloud deployment as a traditional infrastructure often sheds light on areas you may not have considered

When most people look at migrating to the cloud, they're primarily concerned with cost and performance. As much as we'd all like to be able to focus on critically important aspects of cloud computing such as security, availability, and data governance, the questions of how much it costs to run and whether it can keep up with the workload and provide the right features often steal the spotlight.

It's not hard to see why this is the case. Cost and performance are constants that, if out of line with expectations, become problems immediately, whereas considerations like security and availability rise to the top of the pile only when something goes wrong. It's also not always clear to cloud users that some aspects of operating in the cloud are still their responsibility rather than the service provider's.

The easiest way to avoid this trap and make sure that all aspects of the infrastructure are carefully considered is to visualize the cloud infrastructure as you would your on-premises infrastructure. Yes, the cloud is a fundamentally different beast than a traditional infrastructure, but it is also similar in many ways. Although it's true that the cloud service providers you've opted to use may perform many tasks you would have done on premises, you still need to know how they're doing it and make sure your -- and your stakeholders' -- expectations are adjusted appropriately.

Two areas of concern to compare
To help you do just that, I've picked two areas of concern where a cloud deployment needs deeper consideration compared to a typical on-premises infrastructure: user access and disaster recovery.

User access. It doesn't matter how amazing your applications are or how resilient the infrastructure that operates them is. If your users or customers can't access them, they might as well not be up. In a traditional on-premises infrastructure, you might make sure that your campus LAN is deployed with as much redundancy as possible, that sufficient spare desktop hardware is available, and that users can operate remotely if they can't reach the office.

To continue reading, please begin the free registration process or sign in to your Insider account by entering your email address:
From CIO: 8 Free Online Courses to Grow Your Tech Skills
You Might Like
Join the discussion
Be the first to comment on this article. Our Commenting Policies