Databases 31 min read

From Database Development to the New DBA: Strategies for Efficiency, Automation, and Career Growth

The article shares the author’s journey from early database development at DM6/DM7 through MySQL operations at Qunar, offering practical advice on demand‑driven implementation, data‑driven management, intelligent alerting, full‑log analysis, slow‑query risk modeling, high‑availability, and automation to transform traditional DBA work into a proactive, efficient New DBA role.

Qunar Tech Salon
Qunar Tech Salon
Qunar Tech Salon
From Database Development to the New DBA: Strategies for Efficiency, Automation, and Career Growth

Wang Zhufeng, the database director at Qunar, has a deep background in database development and maintenance, having worked on DM6/DM7 at Dameng and later on MySQL source‑code research, automation platforms, and the Inception open‑source project.

Section I – Database Development: Starting in 2009, he joined Dameng as an intern, examined DM6 source code, and later contributed to the ground‑up development of DM7, implementing features such as B‑tree split/merge, job modules, Oracle‑compatible packages, PL/SQL execution, column‑store engines, and MPP‑style data sharding, gaining profound insight into parser, redo/undo, and execution engines.

Section II – Transition to Operations: After three years of development, he moved to Qunar in 2013 to focus on MySQL operations, emphasizing serviceability, direct user demand, and the need to keep databases highly available, which shifted his perspective from feature delivery to reliability and user‑centric service.

Section III – Improving Efficiency: He proposes four key areas: (1) Aligning demand with implementation to avoid idle feature requests; (2) Building systematic data repositories for DB assets to replace reliance on memory; (3) Developing an automation platform to replace manual repetitive tasks; (4) Leveraging all available resources—including colleagues, tools, and leadership—to maximize productivity.

Section IV – DBA Focus: He advises breaking large projects into smaller, deliverable sub‑projects, maintaining clear objectives, avoiding over‑engineering, and regularly communicating progress to prevent “macro‑planning” that stalls execution.

Section V – Core DBA Activities: He outlines concrete practices such as intelligent alerting with low‑threshold filtering, full‑log capture for resource usage, security audit, and troubleshooting; MySQL full‑log analysis; a slow‑query risk index to prioritize optimization; ensuring high‑availability (HA) before containerization; and extensive automation to eliminate manual errors.

Section VI – The New DBA Vision: The “New DBA” should embody high efficiency (machines handle low‑efficiency work), automation, proactivity (anticipating and preventing issues), broad coverage (solving classes of problems), freedom of operation, and personal satisfaction, positioning the role as a strategic, value‑adding partner rather than a reactive fire‑fighter.

monitoringperformanceAutomationDevOpsMySQLDatabase Administration
Qunar Tech Salon
Written by

Qunar Tech Salon

Qunar Tech Salon is a learning and exchange platform for Qunar engineers and industry peers. We share cutting-edge technology trends and topics, providing a free platform for mid-to-senior technical professionals to exchange and learn.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.