Every software system evolves over time. With it it’s APIs. Not every company will always use the most recent release. The most challenging for external partners of an evolving system, such as a database management system, is to keep up with the changing interface. Currently MySQL does not support versioned APIs for the storage engine layer that would partially stay constant over multiple releases. Therefore, you should develop an abstraction layer for the revision engine so we may release version of our engine independently of the server version. Furthermore such an abstraction layer can be used to integrate an arbitrary storage engine to a different MySQL fork, such as Maria or Drizzle. The abstraction layer may be published as a separate project for other projects to use. This task includes the following subtasks:

- Get acquainted with the revision engine architecture
- Analyze the interaction between the revision engine and the MySQL server (we use some actually private functions from MySQL)
- Create and implement a super class for a MySQL instance
- Implement the derived classes for at least 2 or 3 different MySQL versions
- Integrate the abstraction layer into our build system (CMake)

Optional if time still is available:
- Analyze the differences between Drizzle, MariaDB and MySQL releases
- Implement Dirzzle and MariaDB subclasses of the abstraction layer.

For this work you will need knowledge of the C and C++ programming language. All work must be published under the GPLv3 license.

If you have any questions please contact peter@ddengine.org