Gartner: DevOps Market Will Usher in Disruption

This started with development-focused (Dev) suppliers turning to later operations and maintenance-focused (Ops) suppliers to early development-does anyone want a DORA (Development Operations Research and Evaluation) measurement instrument board? , But now it’s free for everyone. The recent acquisition demonstrates that the market realizes that it is the entire tool chain, that is, the system-level solution, that is essential for end users and company executives (that is, customers).

Anyone who is concerned about the application release automation (ARA), application release orchestration (ARO), continuous integration/continuous delivery (CI/CD), PaaS, serverless, microservices, and orchestration tools is aware that there will be an upcoming Collisions will subvert many markets until they subvert the basic definition of these markets. The trend of all developments is to enable companies to deliver application functions to customers faster and more reliably.

As William Gibson famously said, the future is already in sight, but it has not been clearly presented yet. And these markets focus on how to deliver the functionality of the application to the customer's hands faster and more consistently, both now and in the future. From a customer's perspective, this is fine. Customers don't care if your application is delivered through ARO, local environment, cloud, serverless or some kind of magical dust. This is not important.

The problem is here: need to understand the market. All these technologies and technical methods put products: applications in the same business export gate: where customers use them. But customers don't care about stacks, platforms, architectures, or APIs. They care about doing what they want to do, accomplishing the tasks they want to complete, and learning what they want to learn. As Deming said: "Customers learn quickly." They hope that their needs can be met in the first place.

When we focus on the technology of delivering applications (that is, how to develop the functional characteristics of applications), we forget this. That's not the point. The point is that the applications that have been delivered to the production environment and delivered are used by paying customers (that is, what features or applications do for a customer).

There is another problem. Not only is the publishing technology changing the status quo of the delivery experience, but the participants who capture and display the published information are also tending to merge. For example, the traditional work order system became the recording system for the entire process, so it began to become a repository for each process they documented for the company’s application development (ie, create a work order to record new functions, create functions, and release , Close the work order). This systematically formed an external support loop at the organizational level.