Why Is MySQL’s Version Evolution So Slow? Expert Insights on China’s Database Landscape

Introduction

This article records a segment of the "Efficient Operations" series discussion, featuring a Q&A between Oracle ACE director and MySQL expert.

Q3: Why Are MySQL Version Updates So Slow?

Question by Gai Guoqiang: While Oracle progressed from 8i to 12c, MySQL has lingered on version 5 for over a decade. How does MySQL plan its releases, and why does an open‑source product evolve slower than commercial ones?

Answer by Zhou Yanwei: Commercial product cycles often have market‑driven motives; MySQL’s incremental releases are steady and address many issues. Although major version jumps (5.0→5.1, 5.1→5.5, 5.5→5.6, 5.7) bring notable improvements, the core server framework changes little, focusing instead on engine enhancements like InnoDB. Version choice should consider engine features and business needs, reflecting a different philosophy from Oracle.

Q4: Is MySQL’s Domestic Growth in China “Powered by Alibaba, Undermined by Alibaba”?

Question by Gai Guoqiang: Recent rapid MySQL adoption in China benefits from Alibaba’s migration from Oracle, but with Alibaba’s shift to OceanBase and PostgreSQL, will MySQL fade?

Answer by Zhou Yanwei: MySQL’s rise predates Alibaba’s involvement; many companies (e.g., Tencent, Renren) have long‑standing large‑scale MySQL deployments. The open‑source community remains vibrant, with contributions from numerous experts and enterprises. MySQL now powers e‑commerce, payment systems, and is entering financial services, though security and consistency remain critical. Competition from OceanBase and PostgreSQL is healthy and drives further innovation.