Skip to Content

iTKO LISA | SOA Integration, Testing & Virtualization Solutions

icon

iTKO Whitepaper: The Next Frontier for Virtualization: Over-Utilized Systems  members


Whitepaper: August 2009
By Ken Ahrens, Sr. Solution Architect, with Jason English, VP Communications, iTKO LISA

Members: Sign In Required

Member Registration
First Name:
Last Name:
Email:
Work Phone:
Title:
Company:
Address:
City:
State:
Country:
Comments:
 


* Note: You must provide a valid company email to gain access privileges to this site or be a candidate for evaluation. iTKO, Inc. respects your privacy, and will not misuse or share your contact information with any third party. iTKO reserves the right to refuse or restrict access to the LISA Quality Center. By entering this site you agree that you understand our Terms of Use.

By signing up with this site, you can freely access most additional LISA product resources and demos. Items that require a signup are noted by the check mark (members). Please provide an accurate company email. Please note that iTKO uses cookies to track registration; you must allow cookies for your registration to work and to gain access to Resources content. Thank you.

paper

Identifying and eliminating the most critical and costly constraints from the enterprise software development and testing lifecycle.

Hardware virtualization technology is now par for the course in enterprise IT environments. Enterprises can realize immediate cost savings through the use of hardware virtualization to reduce server proliferation, consolidate desktop environments, and run numerous apps with a smaller combined hardware footprint. The key value espoused by leading virtualization vendors (such as VMware, Microsoft, Citrix, etc.) is making better use of "under-utilized" servers and intermittently used capacity that does not demand dedicated system resources to run.

But what are we supposed to do about the kinds of systems that are not good candidates for hardware virtualization? What about the critical over-utilized applications that create bottlenecks among teams that need access throughout the software development and testing lifecycle? Hardware virtualization has a much less compelling value proposition in this scenario.

A strategy to apply in this case is the use of Service Virtualization (SV) to reduce multiple team dependencies on over-utilized systems, allowing them to work in parallel. This article will explain the utilization patterns encountered in enterprise IT environments, and which type of Virtualization (Hardware virtualization, Service virtualization, or a combination of both) should be applied to receive the greatest value. This paper discusses how to apply the principle of under and over-utilization to apply the right type of virtualization for the needs of the business.

Email this page