What’s the Ideal MySQL DBA Learning Path? Insights from an InnoDB Core Developer

This article compiles a Q&A session from the “Efficient Operations” WeChat group, featuring insights from MySQL InnoDB principal developer Lai Zheng.

Q1: Recommended MySQL DBA Learning Path

Lai explains that DBA work differs from development and outlines three learning stages.

1. Concept Understanding Stage

Focus on fundamental database concepts, internal architecture, and transaction models; recommended textbooks include “Database System Implementation” and “Transaction Processing”.

2. Practical Exploration Stage

Hands‑on practice with MySQL installation, initialization, schema creation, and indexing to master common features.

3. Play & Tinker Stage

Apply accumulated experience to solve real problems such as partitioning large tables, tuning buffers, and handling replication issues.

My View of an Operations DBA

An outstanding DBA is passionate, curious, and constantly seeks improvements, finding great satisfaction in advancing the systems they manage.

Q2: Oracle’s View on MySQL Development and Enterprise Edition Pricing

Lai clarifies he does not represent Oracle officially but observes strong internal commitment to MySQL, with many original InnoDB team members retained after the acquisition.

He has no knowledge of plans to make MySQL Enterprise Edition free and believes Oracle’s cautious approach will continue.

Regarding distributed products, internal discussions exist but have not received approval due to potential conflicts with existing Oracle offerings.

Q3: Official Evaluation of MariaDB and PostgreSQL

Lai notes the official MySQL version is relatively conservative for stability, limited external contributions, and political considerations.

Stability is the top priority; risky features are scrutinized.

Most code contributions come from internal staff, making external integration cumbersome.

Political factors within Oracle influence decisions.

While MariaDB and PostgreSQL present clear competition, MySQL leverages its massive ecosystem and focuses on perfecting the most used 80% of features, such as InnoDB performance improvements and added plugins.

Q4: Work and Global Distributed Development at MySQL

Lai describes the InnoDB team of about 20 engineers spread across Europe, America, China, and India, coordinated by a manager named Sunny.

The team works largely remotely using instant‑messaging tools, holds an annual in‑person meetup, and follows a traditional development workflow: design, prototype, code review, QA, and check‑in.

Code reviews are performed by senior members, ensuring high quality without adopting modern agile practices.