Inside MySQL: From a Surprise Interview to Six Years of InnoDB Core Development

Team organization and development culture

MySQL’s InnoDB storage‑engine team was a flat, globally distributed group. During the period described, the team consisted of eleven senior kernel engineers from eight countries (United States, Finland, Australia, Canada, Sweden, India, Bulgaria and China). The flat hierarchy meant that even new engineers could interact directly with senior architects and Oracle leadership. Communication was primarily asynchronous (pigeon, email, phone) with a weekly stand‑up and an annual global team meeting.

Typical bug‑fix workflow

Analyse the bug report, reproduce the failure, discuss the fix with senior engineers and create a new branch in bzr (Bazaar).

Implement the fix and add a corresponding MTR (MySQL Test Run) test case.

Submit the change to ReviewBoard for peer review; the review may require several iterations because reviewers enforce strict correctness.

After approval, run the change on an internal test cluster that builds both debug and release binaries on multiple platforms (Linux, Solaris, Windows, etc.).

When all automated and manual tests pass, merge the branch into the main trunk.

Feature development process

For larger features the workflow adds pre‑implementation steps:

Create a worklog entry that records the task.

Write a High‑Level Design (HLD) document describing the overall architecture and impact.

Write a Low‑Level Design (LLD) that details data structures, algorithms and API changes.

Develop a prototype, integrate it into the code base, and run the same testing pipeline as for bug fixes.

Key technical contributions (selected work‑log entries)

WL#6968 – Added R‑tree index support for InnoDB GIS, enabling efficient spatial queries.

WL#6455 – Implemented full GEOMETRY datatype support in InnoDB.

WL#6745 – Added DML operations (INSERT/UPDATE/DELETE) for R‑tree indexes.

WL#7740 – Enhanced CHECK TABLE to validate InnoDB spatial indexes.

WL#8548 – Introduced Transparent Data Encryption (TDE) for tables, encrypting data at rest.

WL#9290 – Extended TDE to the redo log, protecting transaction logs.

WL#9289 – Added TDE support for undo tablespaces.

WL#9531 – Enabled table‑level encryption and transparent compression via the new data‑dictionary (InnoDB_New_DD).

WL#9535 – Removed legacy InnoDB system tables and updated the INFORMATION_SCHEMA views.

WL#9537 – Implemented import/export of InnoDB tables using the new data‑dictionary.

Transition to Tencent Cloud

After Oracle closed its China R&D centre, the author joined Tencent Cloud’s CDB team, contributing to the TXSQL kernel – a MySQL‑compatible engine used in Tencent Cloud’s database service. The experience from MySQL’s open‑source development process (branch‑based workflow, rigorous code review, extensive automated testing, and design documentation) is applied to the ongoing development of TXSQL.