Vendor Lock-In Issues in Cloud Computing and How to Neutralize Them

Abstract

Despite the benefits of cloud computing, organizations are concerned with interoperability issues when adopting cloud solutions. Literature indicates that vendor lock-in is one of the factors holding back cloud interoperability. One way to reduce vendor lock-in is to incorporate open-source technologies into siloed cloud solutions, yet little is known about the factors to create synergy between open-source technologies and siloed cloud solutions to minimize vendor lock-in issues. The author of this paper explores vendor lock-in dynamics, causes, and downsides, particularly the role open-source technologies such as containers and Kubernetes play in reducing vendor lock-in issues. A vendor lock-in is a state where customers cannot move their services from one vendor to another at will without incurring a substantial amount of switching costs because of proprietary nature of cloud vendors' infrastructure, APIs, and tools. Open-source technologies such as containers and Kubernetes, if they are incorporated into existing siloed cloud solutions, can help businesses migrate workloads from one vendor to another. Containers are lightweight applications that operate as if they own complete CPU, operating system, memory, and network resources. A cloud framework based on open-source technologies like containers and Kubernetes can create synergy between open-source technologies and siloed cloud solutions. The purpose of this qualitative generic inquiry was to understand the factors that hinder organizations from adopting cloud solutions, and to explore factors that will help create synergies between open-source technologies and siloed cloud solutions by leveraging constructs of UTAUT's (Unified Theory of Acceptance and Use of Technology) performance and effort expectations, social influence, and facilitating conditions.