What is the best way to convince management that virtualization isn't always appropriate in producti

Posted by uncle brad on Stack Overflow See other posts from Stack Overflow or by uncle brad
Published on 2010-04-14T02:25:57Z Indexed on 2010/04/14 2:33 UTC
Read the original article Hit count: 257

Filed under:

I work for a small company with a .NET product that was acquired by a medium sized company with "big iron" products. Recently, the medium-sized part of the company acquired another small company with a similar .NET product and management went to have a look at their technology. They make heavy use of virtualization in their production environment and it's been decided that we will too.

Our product was not designed to be run in a virtual environment, but some accommodations can be made. For instance; there are times when we're resource bound due to customer initiated processes. This initiation is "bursty" by nature, but the processing can be made asynchronous and throttled. This is something that would need to be done for scalability anyway.

But there is other processing that we do that isn't so easily modified because we're resource bound for extended periods of time.

How do I convince management that heavy use of virtualization is probably not appropriate for us?

© Stack Overflow or respective owner

Related posts about virtualization