How and why public cloud can be used to get work done
Workloads like websites and new apps are popular candidates for a move to the cloud.
At almost every conference, event or analyst meeting you attend, you'll hear someone discuss how your business can benefit from the Operating Expense (Opex) model, greater agility, and faster deployment speeds offered by the public cloud.
But let's be honest: If you go to your internal IT staff and propose the public cloud, you'll get a lot of pushback. They'll talk to you about a number of issues, most notably security, legal compliance and a loss of control over the company's valuable data. When talking to infrastructure professionals, C-level management and development groups about using the public cloud, the one thing that always comes up is that each group has a different vision of how to use the public cloud, and it's difficult to get their visions aligned. Difficult, but possible.
Today, on-premises (or private cloud) infrastructure is still the most-used solution for production environments. Slowly, we're seeing the adoption of hybrid environments (a combination of private cloud and public cloud where the public cloud is considered an extension of your data centre) where certain front-end workloads are moved to the public cloud.
Workloads like websites and new apps are popular candidates for a move to the cloud, but often the data itself stays on premises in your private cloud. The problem is that debates within the business about using the public cloud are often dominated by discussion of production environments instead of exploring opportunities where the cloud could help save time, effort and money. However, things are looking positive. The public cloud services market in Middle East and North Africa (Mena) region is projected to grow 18.3 per cent in 2016 to total $879.3 million, up from $743.1 million in 2015, according a recent report by Gartner, Inc.
Let's have a look at some common use cases where those benefits can be gained.
Every business needs an environment for testing solutions, development and acceptance. In an ideal world, these should be three separate environments and they should be the same as (or at least very similar to) your production environment.
Unfortunately, the number of enterprises that have the resources available to use best practices is very limited. And those few that have the technical resources to do this often complain that there aren't enough other resources (people) to maintain such environments and that time is limited. Why not use the public cloud for these scenarios? Organisations can create copies of the production environment (at least the important parts of it) in a public cloud and grant access to developers, test engineers, workload owners and more to that environment. After a project is finished, that environment can simply be shut down.
Developers, test engineers and quality control teams love this approach because it allows them to work on production data (while not being on a production environment) and perform testing at scale.
Management likes the pay-as-you-go approach, and more importantly, they find that these scenarios allow the business to work faster and get to market faster with new and improved solutions.
Many enterprises have a change advisory board (CAB) that needs to approve all changes (bug fixes, security patches and functionality enhancements) that will happen in a production environment. The best practice is to implement these as quickly as possible but only after they have been tested thoroughly to prevent any major issues making it to the live environment.
The best way to do this is to mimic your production environment as well as possible when testing changes. Again, this is impossible for most companies due to a lack of resources. Enter the public cloud again. By using copies of the production environment and restoring them into the public cloud, organisations can conduct effective testing and documenting of all those changes and feed that information into the change request plan. What's even better is that potential back-out plans can also be tested, so the organisation can be prepared in case something wrong still goes into production
After all the tests and documentation, the environment in the public cloud can be turned off (or even destroyed) to save on costs.
The writer is regional director, MEA and SAARC, Veeam Software. Views expressed are his own and do not reflect the newspaper's policy.