This article examines how enterprises can adopt DevOps with minimal risk and cost by leveraging agile management, continuous delivery frameworks like the 100‑to‑100 model, Conway’s Law, automation, scripting, and containerization with Docker, while also presenting a recruitment call for DevOps engineers.
This article presents an extensive DevOps glossary covering key terms and practices, a detailed periodic table of DevOps tools, and a skill roadmap outlining the essential knowledge and technologies needed to successfully implement DevOps in modern software delivery.
The article argues that static, five‑level maturity models are unsuitable for DevOps, outlines their three main shortcomings, and presents the data‑driven DevOps Capability Growth Model with its five capability categories and suggested measurement practices.
Continuous delivery is a software engineering methodology that transforms ideas into fast, reliable user releases by linking continuous integration with automated deployment, delivering measurable business value through faster feedback, higher quality, and streamlined collaboration across roles such as CTOs, team leads, product managers, and developers.
This article explains the distinction and relationship between continuous delivery, continuous deployment, and continuous release, emphasizing the need to decouple technical actions from business decisions, focusing on rapid, safe, and sustainable value delivery through well‑designed deployment pipelines and release strategies.
Continuous Delivery and Continuous Deployment are often confused, but this article examines their origins, definitions, and practical distinctions, highlighting how delivery focuses on business‑level release decisions while deployment automates production releases, and explains how they fit within DevOps, CI, and release strategies.
The DevOps International Summit 2024 in Beijing, the sole China‑based global DevOps conference, brings together over 80 leading experts to showcase end‑to‑end practices—from Lean‑Agile, Continuous Delivery, SRE, and microservices to DevSecOps, AI‑driven tooling, and the new Research and Operations Integration Capability Maturity Model—through industry‑focused tracks, hands‑on training, and real‑world case studies across finance, telecom, retail and more.
This article summarizes Wang Qing’s DevOps talk, outlining the current state of DevOps, showcasing concrete case studies from ING, CapitalOne and a major Chinese bank, and providing a step‑by‑step guide to building a practical DevOps toolchain for traditional enterprises.
The article explains that agile development’s essential advantage over traditional waterfall lies in keeping iterations short and work items small—such as user stories, release scopes, and team sizes—to reduce feedback cycles, risk, and communication overhead while delivering continuous value.
This guide explains the core concepts of Continuous Integration, Continuous Delivery, and DevOps, showing why they matter for product teams, how they improve software release speed and reliability, and what steps organizations can take to adopt these practices effectively.
The article explains why many microservice projects struggle with truly independent deployment, shows how centralized E2E tests create a deployment bottleneck, and proposes inline E2E tests and contract testing as practical solutions to preserve independent delivery while ensuring quality.
This article examines why DevOps transformations often fail, outlines five common misconceptions and five proven practices, and provides concrete, data‑driven recommendations—including cultural evolution, small‑batch work, feedback loops, value‑stream collaboration, and waste elimination—to help organizations achieve faster, safer, and more reliable software delivery.
Continuous Delivery is a DevOps practice that automates building, testing, and preparing code changes for production, enabling faster, more reliable releases through extensive testing, cloud‑based environments, and developer‑controlled deployment, while contrasting with Continuous Deployment's automatic production pushes.
The article explains DevOps culture, the shift toward eliminating barriers between development and operations, and outlines key practices such as frequent small releases, microservices, continuous integration, continuous delivery, and infrastructure as code to accelerate innovation while maintaining reliability.
The article explains how DevOps combines culture, practices, and tooling to enable organizations to deliver applications and services more rapidly by breaking down silos between development and operations, fostering cross‑functional collaboration, automation, and continuous improvement throughout the software lifecycle.
The article chronicles Microsoft’s Global Development Platform Engineering team’s transformation from an Agile‑focused process to a DevOps‑driven culture, detailing the 2013 Visual Studio 2013 launch, the ensuing service outage, multi‑region scaling, canary deployments, feature‑flag controls, Git‑based branching, Scrum adaptations, and data‑driven experiments that dramatically improved service reliability and user onboarding rates.
This article examines why many organizations doubt the feasibility of DevOps and continuous delivery, analyzes the root causes behind those doubts, and demonstrates through five detailed case studies how regulated environments, non‑web systems, legacy platforms, and cultural factors can all successfully adopt DevOps practices.
In 2017 Ctrip reorganized its wireless engineering to adopt a lifecycle‑driven, platform‑based approach, introducing the Mobile Tech Platform (MTP) and Mobile Continuous Delivery (MCD) platforms that unified component services, development frameworks, and automated build‑release pipelines for over 20+ apps, dramatically improving efficiency and quality.
The article reflects on how DevOps, Docker, Kubernetes and lean/TOC thinking have transformed over the past two years, explains the three‑step workflow for building a value‑stream delivery pipeline, and offers practical guidance on culture, feedback loops, and handling unplanned work to achieve reliable, business‑focused IT operations.
This article examines Capital One’s open‑source DevOps dashboard Hygieia, explaining its shift to an Open Source First strategy, the value of DevOps visualisation, core functionalities, main views, technical architecture, integration ecosystem, and practical lessons for improving continuous delivery pipelines.
This article explores common release management models—project release, release windows, release trains, and continuous delivery—detailing their advantages, drawbacks, and implementation techniques, and offers strategies for combining these approaches to accelerate high‑quality software delivery in large, complex systems.
This article compares four common continuous delivery deployment approaches—minimum‑service deployment, rolling updates, blue/green deployment, and A/B testing—detailing their workflows, advantages, and drawbacks to help teams choose the most suitable method for their applications.
This article, based on the Chinese translation of the DevOps Handbook, explains the Flow Principle, continuous delivery practices, value‑stream mapping, waste elimination, and Goldratt’s five‑step method for improving DevOps pipelines and achieving low‑risk, fast releases.
Drawing on 40 years of IT experience, the speaker explores DevOps as a transformative practice, discusses its strategic business value, outlines four key discussion areas—including principles, practices, selling to executives, and identifying weak points—and offers practical guidance for cultural and organizational change.
This article explains how Facebook evolved its release engineering process from manual cherry‑picking to a quasi‑continuous push‑from‑master system, enabling thousands of daily code changes, reducing hot‑patches, supporting global engineers, and improving user experience across web and mobile platforms.
User stories are essential for agile development and continuous delivery, and this article explains why they matter, contrasts them with traditional waterfall requirements, and provides a detailed, step‑by‑step template—including examples and acceptance criteria—to help teams transition smoothly from legacy requirement documents to effective, deliverable user stories.
The article explains how transitioning a waterfall‑style project to agile by breaking the work into user stories and using user‑story mapping can provide early feedback, improve continuous delivery, and resolve common pitfalls such as unclear requirements and integration challenges.
This reading note introduces the DevOps three‑step workflow from The Phoenix Project, outlines its three core practices, and summarizes fifteen scenarios illustrating common operational challenges such as untested deployments, missing change records, incident response, and improvement actions.
The article presents Qiniu's Spock continuous delivery platform, detailing its business and technical architecture, pipeline stages from self‑test to release, automation practices, microservice challenges, quality gates, and operational metrics that enable fast, reliable cloud‑native software delivery.
The article explains how DevOps applies lean principles to integrate IT operations and software development, describes artifact‑centric workflows, introduces value‑stream mapping and flow measurements, and shows how these practices enable continuous delivery, feedback loops, and systematic improvement across the enterprise.
This article records Xu Lei's online DevOps talk, outlining his ten‑year journey, emphasizing the importance of managing granularity and engineering decoupling, and providing practical strategies, agile insights, continuous delivery frameworks, Docker benefits, and a Q&A to help teams improve software delivery efficiency.
This article details Meizu's journey from early internet eras to a mature continuous delivery platform, outlining the operational challenges, platform components, standardization, automation, and future intelligent operations to achieve high quality, efficiency, cost control, and security.
The article examines how large financial institutions face technical, procedural, and risk‑control challenges when adopting DevOps, and proposes a three‑stage implementation roadmap—including automation of delivery pipelines, optimization of development models, and continuous‑delivery process refinement—to achieve reliable, rapid software releases.
This article examines how the Cameron‑Quinn cultural framework can be used to assess and shape corporate culture during a DevOps transformation, presenting a detailed case study of Seqr that links cultural diagnostics to continuous delivery practices and operational improvements.
This guide explains how to configure Continuous Build and Continuous Delivery in Visual Studio Team Services (VSTS) for Azure Web Apps, covering source, build, test, and release steps, linking accounts, setting up pipelines, and customizing build tasks for .NET and other projects.
Based on interviews with 16 senior executives from 14 companies, this article highlights that DevOps success hinges on people, process, and technology, emphasizing cultural change, automation, faster releases, higher quality, and the growing impact of cloud and containers on future development practices.
The article explains three software version release strategies—Project Release, Release Train, and Intercity Express—detailing their dimensions of time, features, and quality, discussing advantages, drawbacks, and practical considerations for adopting each mode in modern development and DevOps practices.
This article explores the evolution of continuous delivery, explains its core principles, and presents two detailed case studies from Baidu and Tencent that illustrate how organizational, architectural, and automation improvements can dramatically accelerate software release cycles while maintaining quality.
This article recounts how the Taobao Live team applied agile practices over three months, tracking capacity, lead time, quality, and predictability, and demonstrates measurable improvements in delivery speed, defect reduction, and business metric alignment through focused goals, rapid hypothesis testing, and continuous delivery.
This article recounts the DevOps transformation of a large traditional financial institution, detailing its background, challenges, agile restructuring, legacy system consolidation, continuous delivery pipeline, cloud migration, infrastructure‑as‑code adoption, platformization, and the core principles that enabled successful large‑scale automation.
This article details how Alibaba's RDC platform combines layered automated testing, test‑driven continuous delivery, and comprehensive online quality monitoring to overcome the myth of a single silver‑bullet solution in large‑scale software development.
In this talk, Li Qian details Qiniu Cloud’s end‑to‑end CI/CD journey—from building a scratch‑made quality assurance system and integrating Travis, Jenkins, and Docker, to automating unit, integration, and system tests, establishing quality gates, and achieving ten‑minute rapid deployments and gray releases through metrics‑driven development.
The article describes how a small development team adopts a three‑week periodic release cadence, improves demand management, resolves operational concerns, and standardizes configuration, environment, deployment, and testing processes to achieve continuous delivery with higher quality and lower coordination cost.
To achieve sustainable, low‑cost, high‑quality continuous delivery, teams—especially those under 30 members or working on loosely coupled services—should master core practices such as two‑week iteration cycles, CI pipelines, estimation, planning, and iterative activity management, as illustrated by the Baidu case series.
This article presents a comprehensive overview of a GOPS 2017 Shenzhen talk on DevOps theory and practice in complex business environments, covering the fundamentals of DevOps, cultural transformation, technical architecture, and real‑world case studies that illustrate automation, deployment pipelines, and value‑stream delivery.
This article details how REA Group implements a comprehensive DevOps workflow for its micro‑service architecture on AWS, covering the 12‑Factor principles, toolchain components, automated deployment with rea‑shipper, monitoring, alerting, and the collaborative processes that enable continuous delivery at scale.
The 2017 Puppet State of DevOps Report reveals that high‑performing IT teams deploy code far more frequently, recover from failures dramatically faster, and rely on automation, loose‑coupled architectures, lean product management, and transformational leadership to achieve superior continuous delivery outcomes.
This article explains how DevOps extends beyond bridging development and operations to create a complete, closed‑loop management system that boosts engineering efficiency, supports product and project lifecycles, and enables scalable, automated delivery for enterprise digital transformation.
The article distills Kohsuke Kawaguchi’s QCon Beijing presentation on continuous delivery, covering the evolution of delivery pipelines, DevOps maturity models, practical engineering techniques, and strategic transformation paths, while highlighting Jenkins’ role and offering actionable guidance for teams seeking to adopt efficient, reliable software release processes.
The article traces the impact of Ford’s 1910 assembly line on software delivery, explains Jez Humble’s definition of deployment pipelines, showcases continuous delivery concepts, and presents real-world examples from Baidu, Netflix, and an open-source end-to-end pipeline, highlighting key design points for DevOps transformation.
This article explores why many find DevOps daunting, introduces the ‘Strangling’ model as a step‑by‑step approach to break down barriers, outlines a comprehensive DevOps capability framework, and shares practical case studies from LeTV’s hardware division to illustrate continuous delivery implementation.
The article presents a visual recap of Patrick Debois' DevOpsDays Austin presentation, illustrating the history, culture, practices, challenges, and future directions of DevOps through a series of themed paintings and captions that highlight automation, measurement, feedback loops, and the human side of the movement.
This article introduces a straightforward DevOps implementation framework that maps eleven essential service capabilities across the software development lifecycle, explains why adopting DevOps is a multi‑year journey, and uses a fitness analogy to illustrate how enterprises can progressively build these capabilities.
The article explains Agile software development, Continuous Integration, DevOps, and Continuous Delivery, examines their inter‑relationships from both technical and human perspectives, and offers practical steps, maturity models, and real‑world case insights for teams seeking faster, reliable software delivery.
This article explains how security professionals can adopt DevOps practices—such as cross‑functional collaboration, continuous delivery, and visualized security status—to build a resilient security architecture that aligns with agile development and reduces risk through frequent, small releases.
This article explains how to replace traditional, error‑prone release cycles with a Docker‑based Jenkins pipeline that automates building, testing, image creation, and deployment to Docker, Kubernetes or remote hosts, while sharing practical tips, sample Groovy code, and common Q&A for DevOps teams.
The article describes how a development team transitioned to short‑cycle, periodic releases, outlining the goals, benefits, operational concerns, and a comprehensive set of improvements—including testing strategy, configuration and environment management, and automated deployment pipelines—to maintain quality while increasing release frequency.
The article explains Baidu's traditional project branch management approach, the reasons behind mainline release queues, and summarizes the team's continuous delivery transformation, highlighting clear goals, transparent planning, self‑defined processes, story‑driven development, six‑step CI, and automated testing practices.
This article outlines ten practical DevOps best‑practice steps—including breaking IT silos, aligning performance metrics, achieving real‑time project visibility, automating across the stack, choosing compatible toolchains, starting with small wins, keeping users central, managing change collaboratively, embracing continuous deployment, and building an internal service‑focused culture—to help organizations deliver applications faster and more reliably.
This article traces the evolution of software engineering tools leading to DevOps, highlights common transformation pitfalls, outlines core DevOps practices such as autonomous small teams, traceable toolchains, real‑time metrics, and describes the surrounding ecosystem, offering practical guidance for organizations adopting DevOps.
This article explains the origins and background of DevOps, clarifies common misconceptions about its role and title, outlines its cultural principles, surveys the essential toolchain, and discusses how organizations can adopt DevOps practices beyond just development and operations.
This article explains the origins of DevOps, presents the CALMS and Three Ways frameworks, and organizes practical DevOps principles into four dimensions—people, product, process, and tools—illustrating how they collectively enable continuous, on‑demand delivery of business value.
The article examines the conflict and convergence between ITIL and DevOps in modern operations, outlining DevOps principles, automation in deployment and operations, and three integration models that balance management and execution, while highlighting the distinct values and scenarios for each approach.
This article traces the history of DevOps from Patrick Debois' early frustrations in 2007 through the Velocity conferences, the birth of DevOpsDays, and the rise of continuous delivery, showing how agile principles reshaped IT operations into a collaborative movement.
This article explains the DevOps “Second Way,” emphasizing faster, bidirectional feedback loops, and shows how Docker’s immutable containers, streamlined packaging, and embedded metadata reduce variation, accelerate defect detection, and shorten lead times in service delivery.
This article explains how Docker supports the First Way of DevOps—Systems Thinking—by increasing pipeline velocity, reducing variation, and improving visualization, thereby enabling faster, more reliable software delivery through global optimization of the value stream.
DevOps is a methodology that emphasizes collaboration between development and operations to accelerate software delivery, and while tools alone don’t constitute DevOps, automation and container technologies are essential prerequisites that reduce manual hand‑offs, enable self‑service, and improve feedback loops.
From its origins at the 2008 Agile conference to the modern CALMS framework, this article traces DevOps’s evolution, compares traditional, DevOps 1.0 and 2.0 approaches, and outlines key Chinese practices such as containers, continuous deployment, micro‑services, and enterprise best‑practice recommendations.
This article explains how to use Microsoft Azure and Team Foundation Server to create a container‑based continuous delivery pipeline, covering DevOps culture, the benefits of containers, and three practical scenarios demonstrated in a recorded video.
This article presents a comprehensive case study of the EMC containerized delivery platform, detailing how Docker, Kubernetes, and automated image building are leveraged to achieve continuous delivery for a large‑scale microservices project, and discusses the system’s architecture, image standardization, environment governance, and future enhancements.
This article breaks down comprehensive configuration management—covering code and build artifact versioning, application settings, and environment provisioning—explaining why it is the cornerstone of continuous delivery and offering concrete branch strategies, Git practices, artifact handling, injection methods, and automation tools to achieve reliable, low‑risk software releases.
This article explains how enterprises can overcome manual deployment challenges by standardizing their tech stack, defining mutable and immutable deployment modes, designing an XY‑axis model for system components, and implementing continuous integration, delivery, feedback, and monitoring using tools like Jenkins.
Android's fragmented versions and market‑specific policies make bug fixes and version upgrades painfully slow, but by treating the app as a loader and delivering patch files that replace the Application class, dex files, resources, and native libraries, developers can achieve near‑instant, user‑transparent updates without disrupting the normal release flow.
This article explains the core concepts of continuous delivery, the challenges it faces, practical solutions such as automated testing, CI pipelines, infrastructure‑as‑code tools like Ansible, Docker containerization, and how microservices interact with DevOps to enable rapid, safe releases.
This article summarizes a 2016 Global Operations conference talk that explains how Docker and micro‑services reshape software delivery, covering Alibaba's container usage, cloud‑native principles, continuous integration, immutable infrastructure, and practical tips for deploying containers at scale.
In this talk, Ctrip’s R&D Director Wu Yiting shares how the company’s continuous delivery platform evolved through large‑scale platform launches, major reforms, and the aftermath of the 528 incident, highlighting improvements in security, availability, scalability, and container‑based delivery practices.
Continuous Integration, Delivery, and Deployment form a progressive workflow that automates code testing, staging, and production release, enabling teams to detect issues early, ensure deployable code, and achieve fully automated releases despite challenges like complex topologies and large-scale environments.
This article explains how Docker supports the three DevOps principles—system thinking, rapid feedback loops, and a culture of continuous experimentation—by accelerating development, reducing variation, and improving visibility across the software delivery pipeline.
This article provides a comprehensive overview of DevOps, explaining its purpose, cultural challenges, core principles such as automation, standardization, and configuration, its relationship with cloud, lean and agile, practical steps, metrics, and how it transforms IT delivery into an end‑to‑end business value pipeline.
This article collection explores how Mesos and Docker enable continuous delivery, argues that traditional operations roles are becoming obsolete amid automation and BizDevOps integration, and shares practical CMDB design experiences emphasizing top‑level modeling and ongoing improvement.
The article explains Alibaba's continuous delivery theory, tools, and best‑practice pipeline—including integration, testing, deployment, and release—illustrated with diagrams and a detailed description of how the platform improves software quality, collaboration, and operational resilience in large‑scale cloud environments.
A comprehensive English summary of the DevOps Enterprise Summit highlights the rise of DevOps adoption, real‑world case studies from Target, Ticketmaster, USAA, Capital One, Disney, and IBM, and practical insights on feedback loops, continuous delivery, and scaling DevOps across large enterprises.
This article details the evolution of Mobile Taobao's engineering architecture, development workflow, and quality assurance measures across three phases, illustrating how modularization, automated platforms, and rigorous testing practices enabled high‑quality continuous delivery for a large‑scale mobile application.
This article describes how Docker was employed in a real-world logistics portal project to create a continuous delivery pipeline, integrate Jenkins for CI, standardize container images, automate deployments, and overcome resource constraints, illustrating practical DevOps practices for enterprises.
This article shares a developer’s hands‑on experience with cloud‑based automated deployment, outlining nine concrete rules—from version control of all release assets to treating deployment as a service—that dramatically improve deployment speed, reliability, and scalability across development, testing, staging, and production environments.
This article details a practical case study of using Docker to build a continuous delivery pipeline for a logistics‑industry portal, covering project background, challenges, Docker‑based CI integration, automated deployment strategies, image layering, role‑based scripts, and a private registry setup.
The article examines how modern cloud services, version‑control platforms, and automation tools can be combined to create a unified artifact repository and consistent deployment pipelines across environments, offering practical steps and cultural tips for achieving true continuous delivery.
This article recounts how the Mobile Taobao team transformed a monolithic app into a modular, multi‑bundle system, introduced automated build, test, and release platforms, and refined processes and quality‑assurance practices to achieve fast, reliable continuous delivery at massive scale.
This comprehensive guide, originally a white‑paper by Gene Kim, explains what DevOps is, how it differs from Agile, ITIL and visible ops, outlines its core principles, application domains, business value, and practical patterns for integrating security, QA, and continuous delivery into modern IT workflows.
