What is it about?

The perception of vendor lock-in has shifted from avoidance to embracing it. This paper examines how cloud-agnostic designs and vendor-locked solutions are two sides of the same coin. Vendor lock-in has been modern-day benefits, but is being avoided by some early adopters of vendor-locked cloud tooling and services because of previously failed implementations. This article discusses how the state of vendor-locked solutions is improving, and so is the perception of those adopting vendor-locked DevOps strategies.

Featured Image

Why is it important?

This paper discusses important aspects of cloud-agnostic and vendor-locked DevOps strategies that IT organizations of all sizes can use to devise and implement successful DevOps strategies. Research has found that IT organizations have found contention with proprietary DevOps solutions,. However, there are strategic advantages to vendor-locked DevOps solutions that can realized when properly planned for.


I hope this article brings more interest into the current state of DevOps, both the technical and non-technical aspects of it. Large cloud providers are providing innovative solutions that work well within their respective ecosystems. Too often we as architects and decision-makers avoid these based on early experiences of cloud adoption. There is still much to learn about DevOps, both sociologically and technically. If nothing else, I hope this article intrigues you enough to research deeper and make your own contributions to DevOps research.

William Dunbar
Orderly Ops

Read the Original

This page is a summary of: Vendor-Locked DevOps Strategies, Communications of the ACM, April 2024, ACM (Association for Computing Machinery),
DOI: 10.1145/3633776.
You can read the full text:



The following have contributed to this page