CIOIT Best Practices

Some caveats for CIOs while implementing open-source software

With the advent of open-source software, CIOs could comfortably avoid technology lock-in, as they could go from vendor A to B in case you did not like the support or documentation from vendor A. However, as Barbara Darrow describes in this article appearing in, there are still some caveats that smart tech buyers should consider. Let us take a look at some of them.

Take care when sourcing from one vendor

CIOs must watch out for the following:

  1. When an infrastructure provider offers his own implementation of a tool but fails to submit code tweaks it takes to run that open-source tool on its own system to the broader community, then these changes will not be replicated by other infrastructure provider versions of the same tool. This will limit the businesses options.
  2. Besides, cloud lock-in could occurs when a vendor does not share tweaks he makes to the public cloud provider’s open-source software with the broader community. Open-source is “open-source” in all but name when vendor lock-in occurs i.e. when an open-source product is owned and managed by a single provider in its walled garden. This can hinder smooth migration.
  3. Developers are happy to embrace tools which are easy to get, test and use. Therefore, it is the CIO’s job to keep an eye out for problems which might occur with these same tools down the road.

CIOs must ensure smooth migrations

Stephane Lamoureux, chief operating officer of Virtual Artifacts says that CIOs should ensure that open-source tools are shared with the community without any single vendor control – this will ensure that tools have more universal appeal. If they are “open-source” but do not share with the community, they are not open-source anymore, but proprietary.

Keep the open-source flame burning bright!

Michael Azoff, principal analyst with Ovum Research says that enlightened self-interest should stop all concerned parties from profiting from open-source. Further, open-source will die out if developers refrain from sharing their tweaks, and this will kill their own implementations as well. Lamoureux adds that non-sharers may force users to go to competitors instead.

To view the original article in full, click the following link:

Sapna Hiremath

Sapna S Hiremath is currently working as a Content Specialist Lead for CAI Info India. With experiences of having worked for newspapers after pursuing a Master's in Mass Communication and Journalism, she has worked in the thriving fields of Search Engine Marketing, online shopping and healthcare. Being an avid traveler, she likes being in the serene landscapes of nature, but also likes being around friends.

Related Articles

Back to top button

We use cookies on our website

We use cookies to give you the best user experience. Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.