InformationWeek: The Business Value of Technology

InformationWeek: The Business Value of Technology
e2 Conference & Expo - Boston 2013
= Member Content
Facebook Twitter Share

E-mail | Print | Permalink | LinkedIn | RSS

10 Tools To Prevent Cloud Vendor Lock-in


Nobody wants to be caught in proprietary traps in the cloud. These tools can help you avoid being hemmed in by one vendor.




In enterprise computing, vendor lock-in is too often a fait accompli. Vendor lock-in happens when, for example, a particular company -- such as IBM, Microsoft or Cisco Systems -- becomes the dominant vendor behind a particular technology and develops products that capture the advance with proprietary elements. That prevents its customers from leaving and ensures that only proprietary vendors can continue to capitalize on the technology.

With IBM it was the mainframe. Microsoft for many years dominated end-user computing with its Windows operating system, and Cisco has become the dominant enterprise networking vendor in the Ethernet era.

With the advent of cloud computing, however, customers can avoid lock-in by taking back some of that decision-making power. The cloud is a highly standardized environment, with new standards being added all the time -- such as the DMTF's Open Virtualization Format 2.0 (OVF) -- allowing translation between the proprietary virtual machine formats.

One way to get locked into the cloud is to, say, use only tools that recognize VMware virtual machines or Amazon Web Services VMs based on Amazon Machine Images. These virtual file formats are proprietary. They can be converted and moved around, but you need the right tools to do so. Faced with the prospect that customers might do it themselves, Amazon Web Services has moved beyond recognizing only its own virtual machine format to recognize VMware's as well. VMware and Microsoft recognize and produce some tools that work with each other's file formats. The old lock-in bonds are already being eroded by the nature of cloud computing, and this process will continue.

While there are still many proprietary traps in the cloud -- for example, using only Microsoft .net languages and running workloads only on the Windows Azure cloud -- you don't have to be hemmed in. Tools that recognize .net languages but deploy to public clouds are available. Don't let the convenience of vendor familiarity lead you to lock-in. Cloud computing isn't owned by anyone -- on the contrary, it can and will be the foundation on which many vendors will compete.

Furthermore, enterprise cloud users are eager to tap into a variety of services. They're building private clouds on premises to hold their most critical data, but they also want to interoperate with public clouds for customer-facing activities. That combination is called hybrid cloud computing, and there are multiple tools available.

In general, the best tools go beyond the operating infrastructure to view how well separate servers are running. They provide a view of the application, which uses pooled, or virtualized, resources such as storage and networking. This application-centric point of view addresses such questions as: How well is the application running? Do you need to perform analytics to see if something is going wrong? Do you need to scale it out further? How are the end users seeing the application?

Keeping choice in the hands of the IT manager is an important part of cloud computing. Here are 10 tools that can help you avoid lock-in and keep your enterprise moving forward.

Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).


 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10  | Next Page » 




InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS


Advertisement


InformationWeek Reports

report Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.

report Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.

report Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.

report The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.