Two Key Practices for Implementing DevOps: Granularity and Decoupling

Xu Lei, a Microsoft MVP and Certified ScrumMaster, shares his ten‑year DevOps experience, starting from 2005 when he returned to Beijing and faced source‑control latency, leading him to adopt HTTP‑based TFS and focus on improving team efficiency.

He describes key milestones: the 2008 VSTS Real World event that introduced end‑to‑end delivery, the rise of DevOpsDays (2008‑2009) that popularized the term, and the 2008‑2012 shift from outsourcing to consulting for large enterprises like JD.com, where he helped redesign release processes to reduce risk and improve decision‑making.

The core of his methodology is the "two magic weapons" for DevOps implementation: managing granularity (making work units as small as possible) and engineering decoupling (separating services, components, and environments). He argues that smaller management units lead to faster, more reliable delivery.

He contrasts traditional waterfall management with agile, showing how agile reduces granularity, enables iterative delivery, and aligns planning with variable value and quality. He also explains the software development lifecycle as a design‑driven process, emphasizing the need to treat planning as a flexible, adaptable activity.

Continuous delivery is presented as the engineering counterpart to granularity, ensuring software remains in a releasable state. The author highlights the challenges of system coupling, illustrating them with banking ATM scenarios, and introduces three levels of coupling: code‑level, component‑level, and runtime‑level, advocating microservices and Docker to achieve true decoupling.

Docker is positioned as a solution to the operational complexity introduced by heterogeneous technology stacks, providing a uniform runtime environment that simplifies deployment, testing, and scaling, thereby supporting DevOps goals.

Finally, he outlines a three‑step DevOps workflow—establishing a global view, creating feedback loops, and continuous improvement—supported by visual management, flow reduction, and cultural change. The article concludes with a Q&A covering organizational structure, tool choices, and practical advice for adopting DevOps in various contexts.