This article explains the components, tools, and stages of software delivery pipelines—including version control, continuous integration, continuous delivery, blue/green and canary deployments—while highlighting their automation benefits and offering resources for further learning.
This article examines seven typical misconceptions in software development—from focusing on tasks instead of demand to favoring batch releases over continuous delivery—and offers practical guidance on improving flow efficiency, cross‑functional collaboration, code quality, and automated testing.
The article outlines twenty‑four key capabilities across continuous delivery, architecture, product and process, lean management, and culture that research shows drive superior software delivery performance and organizational outcomes.
The September 7, 2020 technical salon hosted by Qunar's infrastructure R&D team, in collaboration with Keep, gathered over 20 engineering experts to discuss DevOps continuous delivery, test environment management platforms such as Noah, Portal, MPortal, and Thanos, and share practical experiences and architectural choices.
The article outlines ten frequent pitfalls that organizations encounter when adopting DevOps—such as out‑of‑order delivery, misunderstandings of DevOps roles, lack of flexibility, speed over quality, isolated teams, unautomated databases, insufficient incident handling, limited expertise, security neglect, and team fatigue—and provides practical guidance to prevent these errors for more successful DevOps outcomes.
The Continuous Delivery Architect (CDA) course teaches DevOps pipeline design, implementation, and management, covering continuous integration, delivery, testing, deployment, monitoring, security, and the cultural practices needed to boost speed, reduce risk, and earn a certification.
This article details the Agricultural Bank of China's multi‑phase journey to build a broad, end‑to‑end continuous delivery pipeline—covering requirement gathering, architecture design, planning, coding, testing, deployment, and operations—using Microsoft TFS, agile practices, and DevOps metrics to achieve mature, bank‑wide toolchain integration.
The article uses a thought experiment of a computer left idle for a year to illustrate how software architecture must evolve from static diagrams to operationalized, continuously delivered microservices, emphasizing the importance of DevOps, feature toggles, and real‑world resilience.
This article analyzes why DevOps adoption often fails, explores the Agile Flow Model with its four fluency intervals, outlines the necessary organizational investments and challenges for each stage, and presents real‑world DevOps toolchain case studies to guide effective implementation.
The article explains how Continuous Integration, Continuous Delivery, and Continuous Deployment form a standard software development pipeline, highlighting CI’s role in rapid bug detection, CD’s focus on production‑like testing, and deployment automation that keeps code always ready for release.
This article explores the relationship between Agile and DevOps, explaining their origins, narrow and broad definitions, how they address gaps between business, development, and operations, and presenting a capability growth model that highlights continuous delivery and lean principles as shared goals.
This article examines how DevOps adoption transformed the Agricultural Bank’s enterprise‑level R&D management system, detailing its evolution, the operational and cultural shifts introduced, and practical recommendations for integrating DevOps, agile, and continuous delivery at scale.
This article describes Agricultural Bank's "1+1" development model that combines a comprehensive microservice development platform with an end‑to‑end DevOps workflow, enabling rapid, automated delivery of cloud‑native financial applications and achieving industry‑leading continuous delivery maturity.
This article details how a bank's mobile marketing platform adopted DevOps practices—layered testing, automation with an in‑house platform, and metric‑driven measurement—to achieve rapid two‑week iterations, early defect detection, and higher product reliability while outlining future automation goals.
The Agricultural Bank’s Financial Small Shop project showcases how adopting DevOps practices—building automated pipelines, integrating quality gates, and leveraging container technology—cut delivery cycles by up to 80%, accelerated resource provisioning, and achieved industry‑leading continuous delivery maturity across multiple banking services.
The article reviews the book “DevOps Essentials from a Business Perspective,” outlining DevOps origins, core concepts, principles, and practices while emphasizing a value‑stream, business‑oriented approach to accelerate delivery, reduce technical debt, and improve organizational culture.
The article outlines Meizu's transition from a music‑player company to a mobile and internet service provider, detailing the operational challenges faced across three internet eras, the development of a comprehensive automation and continuous delivery platform, and the role of big‑data‑driven insights in improving quality, efficiency, cost, and security.
This article details the Agricultural Bank’s Distributed Application Interconnection (AIR) platform’s DevOps journey, covering small‑granularity development, comprehensive configuration management, end‑to‑end automated pipelines, advanced testing automation, metric‑driven improvements, and the successful third‑level continuous delivery assessment across multiple projects.
Facing fragmented credit product development, Agricultural Bank built a micro‑service‑based credit middle platform and implemented a comprehensive DevOps pipeline—featuring lightweight branching, visualized continuous deployment, end‑to‑end traceability, three‑layer quality gates, and metric‑driven automation—that dramatically improved delivery speed, quality, and operational efficiency.
This article examines common pitfalls in software development—such as confusing task volume with real demand, over‑emphasising resource utilization, and relying on batch releases—and offers practical guidance on demand‑driven collaboration, flow efficiency, cross‑functional teams, automated testing, and continuous delivery to create higher‑value outcomes.
This article explains the challenges of traditional enterprise IT delivery, outlines the role of DevOps and continuous delivery, and presents a detailed case study of a large financial firm that achieved six‑fold deployment speed gains through standardized pipelines, artifact management, and automated cross‑team notifications.
The article details how China Construction Bank's Pacific Credit Card Center adopted the national DevOps standard, achieved a level‑3 continuous delivery maturity, and transformed its internet platform with a micro‑service architecture, automated pipelines, and measurable performance improvements.
The article details Baixin Bank's participation in the GNSEC 2020 summit, its successful DevOps Level 3 assessment across five key projects, the measurable efficiency gains achieved, and expert interview insights on the challenges and future plans for DevOps adoption in the banking sector.
The article details TaiKang Insurance's journey through the GNSEC 2020 DevOps summit, its successful Level‑3 continuous‑delivery assessment, the technical and organizational challenges overcome, measurable gains such as 300% demand parallelism, 50% faster response, and future plans to expand DevOps practices across the enterprise.
The article details the GNSEC 2020 summit, the release of the seventh batch of DevOps standard assessments, Pudong Development Bank’s successful Level 3 continuous‑delivery evaluation, and an in‑depth Q&A revealing the bank’s DevOps transformation, challenges, and future plans.
Baoxin Software’s Deputy Director of the Industrial Internet Research Institute discusses how their ePlat data collaboration platform passed the national DevOps standard’s Level 3 continuous delivery assessment, revealing the metrics, challenges, and strategic benefits that propelled their software delivery to a leading domestic benchmark.
Anxin Securities’ mobile trading platform recently passed the third‑level DevOps continuous‑delivery assessment, revealing how the firm built an organization‑wide toolchain with open‑source solutions, aligned with CMMI and agile practices, and plans to expand DevOps standards across all its systems.
At the GNSEC 2020 summit, China’s Agricultural Bank showcased how its five diverse projects—ranging from credit middle‑office to personal online banking—successfully achieved Level 3 of the national DevOps continuous‑delivery standard, revealing the challenges, strategies, and future plans behind their rapid, enterprise‑wide transformation.
The article details how China People's Insurance (PICC) leveraged a distributed micro‑service architecture, AI integration, and a DevOps maturity model to attain a level‑3 continuous delivery rating, illustrating the practical benefits, metrics, challenges, and future plans of their transformation.
This article presents a curated collection of 54 essential books covering Agile, DevOps, Lean, continuous delivery, software architecture, testing, organizational learning, and entrepreneurship, guiding readers through a systematic "read thin, read thick" approach to build a comprehensive knowledge framework.
This article explains the core DevOps philosophy—including Lean, Agile, CI, CD and Continuous Delivery—describes its five‑point framework of culture, automation, lean‑agile core, measurement and sharing, and details a three‑step implementation method of fast flow, fast feedback, and continuous learning with practical practices and examples.
In this interview, DevOps veteran Dong Yue shares his journey from a curious Tsinghua student to a leading architect at Alibaba, his influential books on configuration management, the creation of China’s first DevOps maturity model, and practical advice for young engineers seeking purpose and impact.
This interview chronicles Dong Yue’s path from a curious Tsinghua student to a DevOps leader at Alibaba, highlighting his early fascination with software engineering, influential books, the creation of the Aone platform, the national DevOps maturity model, and practical advice for aspiring technologists.
This article explains the drawbacks of the traditional software release process, introduces continuous integration, delivery, and deployment concepts, compares GitLab CI/CD with Jenkins, and outlines the architecture, configuration files, and advantages of using GitLab’s built‑in CI/CD platform.
This article explains the shortcomings of the traditional software release process, introduces continuous integration, delivery, and deployment concepts, compares GitLab CI and Jenkins features, and outlines the advantages, architecture, and practical usage of CI/CD pipelines for DevOps teams.
The article analyses the 2020 Chinese DevOps survey, highlighting the current maturity of agile management, continuous delivery, technical operations, application design, and security, while sharing practical experiences, tool choices, and common challenges faced by enterprises during DevOps transformation.
This article provides a comprehensive overview of DevOps concepts, including definitions of CI, CD, continuous deployment, version control, tooling, implementation steps, benefits, and distinctions from Agile and Lean IT, offering guidance for effective adoption and interview preparation.
This article presents a comprehensive overview of the 14 most popular CI/CD tools, describing their main functionalities, licensing models, and official websites to help teams choose the most suitable solution for fast and reliable software delivery.
This case study examines JD.com’s evolution into a technology‑driven enterprise, detailing its corporate culture, the “ABCDE” technology strategy, the implementation of DevOps and agile practices through the CALMS framework, and how unified continuous‑delivery platforms and operational metrics have driven growth, efficiency, and pandemic response.
This article explains the core concepts of continuous integration, delivery, deployment, and testing, outlines common challenges such as limited environments and ownership issues, and highlights why CI/CD is vital for improving developer productivity, code quality, and faster software releases.
China’s first global DevOps Capability Maturity Model, jointly created by leading industry and academic partners, defines best‑practice assessments across agile development, continuous delivery, technical operations, security, and tooling, offering enterprises a concrete roadmap to mature their DevOps processes and achieve faster, reliable software delivery.
This article presents a comprehensive analysis of Ant Financial’s financial‑grade R&D efficiency practices, covering industry challenges, the SOFAStack‑LinkE platform, agile and DevOps methodologies, continuous integration, testing, deployment, release strategies, cloud‑native transformation, and consulting solutions for improving development productivity and reliability.
This article explains continuous delivery as a software engineering practice that shortens release cycles, improves stability, and enhances team collaboration through standardized processes, automation, and retrospectives, while highlighting its main advantages, business‑management considerations, and the importance of regular post‑mortem analysis.
This article explains cloud‑native fundamentals, the evolving role of DevOps in the cloud‑native era, and presents a detailed GitOps secure release model with architecture diagrams, branch‑to‑environment mappings, Jenkins pipelines, and supporting tools for efficient, safe application delivery.
Feature flags enable controlled system changes, allowing teams to monitor business and technical metrics, quickly roll back harmful updates, and operate within a rapid feedback loop that informs subsequent iterations, though many modern product teams struggle to integrate flag platforms with analytics systems for richer insights.
Feature flags enable controlled system changes, allowing teams to observe business and technical impacts, retain beneficial updates, quickly roll back harmful ones, and continuously learn through a fast feedback loop that guides subsequent modifications.
The article explains how focusing on a single critical point—such as the deployment stage—can dramatically accelerate an organization’s end‑to‑end DevOps transformation, illustrated with JD.com’s journey from manual releases to an automated, high‑efficiency continuous delivery platform.
Meituan Waimai transformed its release process from a six‑week serial model to a hybrid bi‑weekly and weekly cadence, automating version management, CI pipelines, and deployment to enable continuous delivery that rapidly ships features for over 30 million daily orders while maintaining high quality.
Implementing an effective CI/CD pipeline involves understanding continuous integration, delivery, and deployment, recognizing their benefits such as faster feedback and early error detection, and following key stages—from commit and build to testing and production deployment—while selecting appropriate tools and practices to streamline software delivery.
The article recounts Jiangsu Telecom’s successful Level‑3 DevOps continuous delivery assessment at the 2019 Beijing Operations Conference, highlighting the role of standardization and tooling, sharing interview insights on the intelligent pre‑processing system, and outlining the broader DevOps standard ecosystem in China.
ICBC’s Smart Investment (AI‑投) project recently passed the third‑level DevOps continuous‑delivery assessment, showcasing a cloud‑native, AI‑driven architecture, a comprehensive DevOps toolchain, and a feature‑branch workflow that together enable rapid, reliable releases and set a new benchmark for financial‑sector software delivery in China.
CITIC Bank’s software development center shares how three flagship projects passed the level‑3 DevOps continuous‑delivery assessment, revealing the role of standardization, tool empowerment, agile practices, and container‑based pipelines in accelerating delivery and boosting team morale.
This article examines how Ctrip Hotel implements DevOps testing—from business and technical drivers, through continuous delivery challenges, to the design of the Moss platform, its toolchain, data center, and future automation goals—highlighting practical solutions for rapid, high‑quality software delivery.
This article details how a logistics startup overcame severe product‑delivery bottlenecks by reshaping team cognition, visualizing value streams, limiting parallel work, and adopting Specification‑by‑Example, resulting in a ten‑month cycle with 52 iterations, a 15‑billion‑yuan revenue surge, and dramatically faster, higher‑quality releases.
The 3rd Hangzhou Testing Salon, part of Youzan’s eighth technical series, featured Youzan leaders discussing continuous‑delivery product evolution, platform design, and cost‑effective testing environments, with videos and PPT available, while future Alibaba and KuJia sessions will be announced soon.
In this detailed recap of the 2019 GOPS Shanghai conference, three seasoned DevOps experts dissect what makes a successful DevOps practice, covering business goals, product design, delivery pipelines, reducing wait times, automation, cultural change, tooling, and practical implementation steps.
Gaode’s continuous delivery journey transformed its multi‑stage release process into a standardized, automated pipeline that delivers backend services within an hour, cuts manual effort, boosts release efficiency by up to 90%, and embeds early quality checks and data‑driven insights for faster, higher‑quality business value.
This article presents a comprehensive case study of Etsy’s evolution in quality assurance, engineering culture, continuous integration, continuous delivery, and cloud migration, detailing the team structure, testing strategies, four core engineering principles, tool development, and the benefits of rapid, automated deployment pipelines.
The article explains how to assess a project's code quality using four key metrics, compare error density between codebases, manage legacy code with the Scout Camp principle, and choose reasonable thresholds such as cyclomatic complexity, providing a practical approach for continuous delivery.
This article details Beijing Mobile's successful Tier‑3 DevOps standard assessment, showcasing their micro‑service, container‑based performance management system, the role of standards and tooling in boosting efficiency, and insights from a Q&A with senior engineers on implementation challenges and future DevOps prospects.
This article outlines Alibaba’s approach to scaling R&D efficiency across its 50,000‑engineer workforce, detailing the challenges of large‑scale development, agile and DevOps practices, value‑focused delivery, and systematic tools that enable sustained high‑quality software production.
The Agile Release Train (ART) is a long‑lived, cross‑functional team of Agile teams that aligns business and technology missions, follows fixed cadence and shared principles, and delivers continuous value through defined roles, DevOps practices, and a continuous delivery pipeline within the SAFe framework.
The article argues that programmers should devote the majority of their limited time to mastering transferable fundamentals such as clean code, design patterns, and domain‑driven design, while allocating only a small portion to learning ever‑changing frameworks and tools, illustrated through a mentor dialogue and book recommendations.
This article presents a comprehensive case study of Huawei's three‑generation R&D evolution, SoftOpen Cloud's lean DevOps philosophy, detailed practices such as Scrum, Kanban, branch strategies, continuous delivery pipelines, tool support, and a comparative analysis of competing DevOps platforms.
A survey of 14 IT experts reveals how automation testing addresses real-world challenges such as data leaks, security scaling, rapid digital transformation, regression bottlenecks, continuous delivery, UI complexity, and cross-industry efficiency, highlighting its impact on product quality and time-to-market.
The article details the GNSEC summit where China Merchants Bank earned a Level 3 DevOps Capability Maturity Model certification, outlines the seven evaluated projects, explains the world’s first DevOps standard, and shares an in‑depth interview revealing the bank’s DevOps promotion strategy and challenges in the financial sector.
This article explains the origins of Agile and DevOps, compares their goals and practices, highlights their overlapping principles such as collaboration, small‑batch delivery, visualization, and continuous learning, and outlines how DevOps extends Agile to improve software delivery and operations.
The article explores how software architecture, traditionally depicted with static diagrams, must be continuously operationalized and evolved—illustrated by a thought experiment of a dormant computer, real‑world airline case, and the rise of microservices and DevOps practices—to remain viable in a constantly changing ecosystem.
The 2019 State of DevOps report reveals how organizations can benchmark their software delivery performance, adopt two key efficiency models, and implement lightweight change‑management practices to move from low‑efficiency to elite‑efficiency status, backed by data‑driven insights and actionable steps.
This article examines how Amazon revamped its organization, migrated from a monolithic to a micro‑service architecture, built unified tooling such as APOLLO, and automated its delivery pipeline, enabling thousands of deployments per day while also promoting a DevOps hackathon for practitioners.
This article examines Google’s corporate values, development history, culture, and detailed DevOps and Site Reliability Engineering practices—including continuous delivery, SRE responsibilities, and Google Cloud Platform CI/CD tools—to illustrate how the company achieves 24/7 reliable service deployment at massive scale.
This article examines Amazon’s evolution—from its early focus on books and relentless customer obsession to the adoption of micro‑service architecture, two‑pizza teams, and a high‑velocity continuous delivery pipeline—illustrating how strategic cultural and technical choices drive massive operational efficiency.
This article explains China’s inaugural DevOps Capability Maturity Model, its continuous delivery requirements, the assessment process, participating enterprises, and how organizations can apply for certification in the upcoming evaluation round.
This article describes Ctrip’s large‑scale continuous delivery system, its benefits for efficiency, quality, reliability and team collaboration, the evolution of its deployment models, the design of a unified Jenkins‑based build platform, and practical experiences running Jenkins on Kubernetes with elastic scheduling and workspace management.
This article compares classic Git Flow with trunk‑based development and introduces a hybrid Omega branching model, explaining each branch type, their pros and cons, and how the new approach balances rapid iteration with release stability.
The article argues that without Test‑Driven Development (TDD) or its extension ATDD, DevOps initiatives and continuous delivery pipelines lack reliable automated testing, making releases risky despite high code‑coverage metrics.
YouZan’s middleware testing team, divided into six specialized groups, employs a left‑shift quality assurance system spanning requirements, development, testing, release, and go‑live phases—leveraging over 10,000 automated test cases, a bus‑based release framework, chaos engineering, continuous delivery, and comprehensive monitoring tools to ensure resilient, high‑quality services.
WeChat, China’s top social app with over a billion users, has applied DevOps practices to dramatically improve development efficiency, code quality, and accelerate the feedback cycle from requirements to delivery, while confronting real‑world challenges in tooling, processes, reliability, and automation costs.
The article explains how LinkedIn applied the 10X rule—setting ambitious, ten‑fold goals—to overhaul its mobile development process, introducing weekly releases, aggressive testing, static analysis, distributed builds, and feature‑flag‑driven deployments to dramatically improve engineering efficiency and product delivery speed.
Senior Director Wang Xiaoxiang of Qunar shares how a data‑centric, metrics‑driven DevOps approach transformed the company's engineering efficiency, detailing Qunar’s measurement model, indicator definitions, technology choices, results, and strategies for leveraging metrics to continuously improve the software delivery lifecycle.
This article examines Alibaba’s journey to achieve a 7 × 24 hour continuous delivery channel, detailing how system design, architecture evolution, configuration management, testing automation, and cultural shifts together boost R&D efficiency and enable rapid, reliable code iteration across large-scale teams.
Facing a legacy .NET and Oracle‑based vendor system serving ten countries, a global bank doubled release frequency and halved failures by separating small data‑patch deployments from monthly releases, automating testing and deployment with Jenkins, GitHub, and custom scripts, and aligning release windows to regional business hours.
A major bank transformed its legacy vendor‑managed .NET/Oracle applications by automating data‑patch deployments through Git, Jenkins, and custom database tools, enabling weekday releases, reducing manual effort, cutting overtime, and achieving continuous delivery despite outdated systems.
The article explains that selecting a Git branching model—Git‑flow, GitHub‑flow, or Gitlab‑flow—depends on a team's engineering capability and collaboration discipline rather than size, describing each model’s suitability, trade‑offs, and real‑world examples such as Facebook’s trunk‑based delivery.
This article details Ctrip's large‑scale continuous delivery practice, describing their deployment pipeline, unified build platform, Jenkins integration, Kubernetes‑based elastic agents, monitoring, and the challenges and improvements they encountered while handling thousands of daily deployments across multiple environments.
This article details Ctrip's mobile app release practice, covering the organizational structure, step‑by‑step release workflow, the MCD continuous delivery platform, key success factors, and insights drawn from years of large‑scale mobile deployment across dozens of business units.
This article details a practical, production‑grade Spark CI/CD workflow using GitLab and Jenkins, covering source management, multi‑branch release strategies, automated testing, gray‑release, hot‑fix handling, and rollback mechanisms for large‑scale deployments.
This article traces the evolution of DevOps from Patrick Debois' 2007 frustrations as a Belgian IT consultant through key conferences, blogs, and publications that shaped the DevOps movement, highlighting its roots in Agile practices and the convergence of development and operations.
This article defines R&D efficiency as the ability to continuously deliver value quickly, explains the problem of efficiency silos, introduces five comprehensive measurement groups, showcases a defect‑trend chart example, and presents the practical 2‑1‑1 target framework for improving development speed and quality.
The article outlines the three core principles of software configuration management—versioning everything, sharing a single source of truth, and standardizing with automation—explaining how they underpin continuous delivery pipelines and offering practical validation questions for teams.
The article presents a comprehensive case study of the C3 credit system’s agile and DevOps transformation, detailing the challenges in configuration and version management, the design of a dual‑mode development and delivery platform, automated pipelines, quality controls, full‑process traceability, organizational rollout, and the resulting efficiency gains, while also including a DevOps recruitment notice.
The article argues that developers should devote the majority of their learning time to timeless fundamentals—design patterns, clean code, and architecture—rather than constantly chasing the latest frameworks and tools, using personal anecdotes and a mentor dialogue to illustrate the point.
The article explains three software release models—Project Release, Release Train, and Intercity Express—detailing their constraints, benefits, drawbacks, and how they relate to branch strategies and delivery frequency in continuous delivery practices.
This article outlines Ant Financial’s engineering practices for achieving fast yet stable continuous delivery of financial‑grade internet products, covering industry challenges, agile delivery methods, risk‑controlled innovation, and the AntLinkE platform that integrates DevOps, data analytics, and service support.
This article explains how senior engineers must go beyond continuous delivery to ensure that what they ship delivers real value, describing the relationship between continuous delivery and business innovation, the growth‑flywheel model, the gate‑keeping framework, impact mapping, and the Biz‑Dev‑Ops practice for data‑driven, iterative product development.
Microsoft's Core Services Engineering (CSE) team transformed from a waterfall development model to an agile, DevOps‑driven process using Visual Studio Team Services, introducing engineering fundamentals, a four‑level maturity model, a scaled agile framework, and a rotating Directly Responsible Individual role to accelerate delivery, improve quality, and enhance customer satisfaction.
This article explains Alibaba’s “2‑1‑1” vision for accelerating continuous delivery—delivering 85% of requests within two weeks, developing them within one week, and releasing within an hour—by visualizing end‑to‑end value streams, limiting parallel work, and applying lean, agile practices to improve flow efficiency.
This article explains agile development’s core business goals of faster value delivery and effective learning, defines agile as early value delivery and adaptive response, and presents a comprehensive five‑group metric system—including release capability, demand response cycle, throughput, built‑in quality, and external delivery quality—to assess and improve continuous delivery performance.
The article explains how adopting a fixed rhythm through agile development, continuous delivery, and productivity techniques like the Pomodoro method can help teams manage energy, improve work efficiency, and consistently deliver business value despite time’s inherent uncertainty.
This article details the evolution and practices of a continuous delivery engineering system in Android development, focusing on reliability, automation, and tools like GitLab and OkCheck.
