Reexamining DevOps and Platform Engineering: Why Developers Resist Operations and Key Success Factors

Introduction

This article re‑examines DevOps and the newer notion of Platform Engineering, aiming to clarify their definitions, compare their goals, and provide insights for teams building internal development platforms (IDPs).

DevOps Goals and Limitations

Since its inception in 2009, DevOps has emphasized collaboration, automation, and faster, higher‑quality software delivery. After more than a decade, many organizations still face high deployment costs and tooling friction, indicating that DevOps alone does not prescribe a concrete evolution path.

What Is Platform Engineering?

Platform Engineering is a discipline that designs and builds self‑service toolchains and workflows for developers, abstracting away infrastructure complexity. Its core idea is to provide reusable, scenario‑driven capabilities that let engineers solve problems without direct platform team involvement, thereby accelerating delivery and improving user experience.

“Platform engineering is the discipline of designing and building toolchains and workflows that provide self‑service capabilities for software engineering organizations in the cloud‑native era.” – platformengineering.org

Unlike DevOps, which focuses on culture and automation, Platform Engineering concentrates on constructing a reusable platform architecture that offers a self‑service experience.

Industry Recognition

Gartner has listed Platform Engineering as a top strategic trend in 2023 and again highlighted it in the 2024 technology trends, underscoring its growing importance.

Why Developers Reluctantly Take on Operations

Focus on core development tasks.

Lack of interest or expertise in operational work.

High responsibility and risk associated with production incidents.

Insufficient, user‑friendly tools and platform support.

The Essence of Operations

Operations ensures system safety and stability, requiring 24/7 monitoring, incident response, resource management, and routine maintenance. Recent high‑profile outages (e.g., Alibaba Cloud in November and Didi’s Kubernetes upgrade failure) illustrate the critical impact of operational failures.

Key Reflections

Safety must never be sacrificed for speed; both developers and operators share responsibility for preventing costly incidents.

Success Factors for Platform Engineering

To promote Platform Engineering within an organization, consider:

Defining a clear platform scope and avoiding duplicate tooling.

Establishing a developer‑centric platform culture.

Setting goals around scenario‑driven, self‑service capabilities.

Assigning explicit owners for each platform domain.

Prioritizing developer‑driven requirements and user experience.

Providing rich APIs and comprehensive documentation.

Characteristics of Effective Internal Tools

Productization: Treat internal tools as products serving the entire engineering organization.

User Experience: Offer intuitive GUIs and APIs while hiding backend complexity.

Integration: Consolidate monitoring, logging, alerts, and other observability aspects into a single workflow.

Self‑service: Enable engineers to accomplish tasks without platform team assistance.

Measuring Platform Engineering Success

Metrics can be grouped into three dimensions:

User dimension: weekly active users, number of business units enabled, NPS.

Product dimension: access latency, execution efficiency, success rate.

Organization dimension: cycle time, mean time to recovery, etc.

Future Outlook

Globally, companies like Google, Spotify, Netflix, and Walmart are actively adopting Platform Engineering. The CNCF has published a Platform Engineering maturity model with five dimensions and four levels. In China, industry groups are drafting standards tailored to local needs.

Gartner predicts that by 2026, 80% of software engineering organizations will have dedicated platform teams, with 75% offering developer self‑service portals.

Recommended Operations Tools (Internal)

Resource Management (Taishan CMDB)

Provides unified resource data, tagging, multi‑dimensional queries, and standard APIs for automation.

Operations Foundation (Taishan Tiger Symbol)

Unified host‑agent management platform offering Open‑API for monitoring, chaos engineering, bastion host, and serverless command execution.

Host Security (Taishan Bastion Host)

Enterprise‑grade bastion platform with comprehensive permission control and security auditing.

Operations Automation (Taishan Qilin)

Automation platform enabling self‑written code, command execution, and workflow orchestration to reduce manual effort.

Cloud Management (Taishan Cloud Management)

Unified management of public‑cloud and private‑cloud resources, delivering a self‑service T‑PaaS experience.

For further discussion or to join the technical community, scan the QR code below.