Sunday, September 25, 2011

Avoid Vendor Lock-in In the Cloud

http://gigaom.com/2011/09/24/5-ways-to-protect-against-vendor-lock-in-in-the-cloud/?utm_source=#frankguillen

This article points out the need to avoid vendor lock-in in the cloud. If you allow your company to get locked in, it can and will mean price increases and loss of flexibility, which is why you went to the cloud in the first place. It cites the following steps that can help with this issue:
  1. Avoid vendor  lock-in at all cost - if not done, it can result in cost increases that will rob your company of capital needed to invest in growth.
  2. Know thy PaaS - use multiple PaaS providers to ensure flexibility.
  3. Ask hard questions about redundancy and system architecture - the same questions your customers ask you about your solution. Don't settle.
  4. Pick code that's easier and faster to modify - many vendors impose coding technology constraints on their customers (ex. Force.com - Apex).  
Proper due diligence is required to not fall into this trap.

1 comment:

  1. I have to agree but it all depends upon exit strategy and still going out for RFQs on projects at hand... Vendor lock-in has to bring value to the company. The relationship is so good and value is there and there getting an exclusive agreement with a better terms make sense.. But where most companies fails:
    1) Research
    2) Confirming the research
    3) Checking real case scenarios with vendors (are they what they are and provided with track record).

    At the end, I do not want to lock in because there is the potential for increased cost over the long run. But it could go the other way (since the cost could increase and you are keeping the pricepoint the same when you consider inflation, IT purchases, etc.)

    ReplyDelete