Understanding DevOps: Principles, Differences from Traditional Models, Challenges, and Measurement

At the 2017 Operations/DevOps Online Technology Summit, senior Alibaba Cloud platform R&D expert Lian Ming delivered a talk on DevOps, covering its definition, differences from traditional models, challenges such as finding balance points, responsibility allocation, and assessment, and concluding with a brief summary.

The discussion begins with recent high‑frequency operations incidents—from data deletions to ransomware attacks—highlighting the shift from manual operations to cloud‑based, global, process‑driven, and fine‑grained practices, and questioning the future role of operations amid AI advancements.

What is DevOps?

DevOps is an engineering model that maximizes engineering efficiency by clearly dividing responsibilities among development, operations, testing, and pipeline roles.

The core of DevOps is role division rather than organizational restructuring; vertical hierarchies do not guarantee the required division, nor do horizontal structures automatically imply traditional divisions.

DevOps aims to maximize engineering efficiency and is a methodology that exists to achieve that goal.

Differences between DevOps and Traditional Models

In the traditional division, product designers (PD) propose requirements, developers code, SCM packages, QA tests, and operations (OPS) deploy, resulting in a clear hand‑off chain.

Advantages: clear division and responsibility, guaranteed quality, layered controls, and easy governance.

Disadvantages: high communication and waiting costs, each stage can become a bottleneck, and OPS often ends up as a “clean‑up” role, leading to bugs and inefficiencies.

In the DevOps division, the workflow is driven by tools: developers write code, then automated packaging, testing, deployment, and monitoring take over, while SCM, OPS, and QA act as overseers ensuring the toolchain runs smoothly.

Benefits: reduced communication and waiting risks, shorter delivery cycles, and developers own the delivery, avoiding hand‑off disputes.

Drawbacks: many participants increase risk, tooling must support diverse business scenarios (costly), and when tools fail, manual intervention is required; excessive developer authority can lead to “warlord” situations.

Key Challenges and Issues in DevOps

Finding a Balance Point

DevOps seeks maximum engineering efficiency, yet efficiency and stability often conflict; the challenge is to improve efficiency without compromising stability.

When a single team handles both business KPIs and stability KPIs, it reverts to the traditional split.

Responsibility and Authority Allocation

Developers focus on coding, while packaging, testing, and release are auxiliary tasks; the question is how much non‑coding effort developers should spend and how responsibilities are shared among teams.

The core is tooling, which must glue processes together, be extensible, and require ongoing support from operations, testing, and SCM teams to evolve sustainably.

Constraints and Assessment

After breaking the old balance, a new equilibrium must be established; developers gain more voice, but must be constrained internally or externally.

Each organization must find its own balance, allocate responsibilities, and define assessment mechanisms to sustain the DevOps model.

How to Measure DevOps

DevOps can be evaluated from four perspectives:

Engineering Efficiency: time from requirement receipt to production release.

Stability: high efficiency without stability leads to rapid failure.

Non‑development Work Ratio: a high proportion indicates risk of failure.

Business Scale vs. Operations Staff Ratio: e.g., each Google SRE manages ~2,000 machines.

Summary

1. After automation, many traditional ops roles may disappear, which is an inevitable result of progress.

2. DevOps has no single best practice; focus on case context and business background, as DevOps is a method, not an end goal.

3. Neither DevOps nor traditional models are inherently good or bad; suitability depends on the specific situation.