Perth, Western Australia - 6th to 10th January 2014

<-- Back to schedule

Past, Present and future of MySQL and variants

When MySQL was owned my MySQL AB it was doomed because it was a "toy" database. Soon after Sun bought MySQL AB for $1billion there was concern that MySQL was doomed at Sun.... and when Oracle bought Sun things looked even worse. That being said, the truth is a lot more nuanced than what has been widely reported.

We'll look at why MySQL development has been so centralized and where it may be opening up. Who is doing actual development? What are they working on and is it going to help you with new or existing applications? How are they interacting with distributions and has there been any change in adoption?

Why have so many hardware and software "next big things" in the MySQL world just vanished and does this have an implication for the MySQL variants of today?

This is an insiders look at where the MySQL world has come from and where it's going. We'll look at Oracle MySQL, MariaDB, Percona Server and other MySQL distributions.

Why do options other than Oracle MySQL exist? Are they seeing any significant adoption and is Oracle's MySQL 5.6 seeing any adoption or when may it see any?

Should you switch to MariaDB? Is MariaDB becoming an entirely different database server? What other options do you have?

Stewart Smith

Stewart Smith is Director of Software Architecture at Percona, joining in 2011 with a deep background in database internals including MySQL, MySQL Cluster, Drizzle, InnoDB and HailDB.

Prior to joining Percona, Stewart worked at Rackspace on the Drizzle database server focusing on getting it through a critical milestone of a stable Generally Available (GA) release. Prior to Rackspace, he worked on Drizzle as a member of the CTO Labs group inside Sun Microsystems.

As one of the founding core developers of the Drizzle database server Stewart has deep expertise in the code base. He had direct involvement in significant refactoring of the database server including removing the FRM, the InnoDB storage engine, xtrabackup, the storage engine API, CATALOG support and countless bug fixes. He also maintains HailDB, a shared library offering a NoSQL C API directly to InnoDB.

At Sun Microsystems, and MySQL before that, Stewart was a Senior Software Engineer in the MySQL Cluster team working on core code and features inside the MySQL Server and the Cluster codebase working on projects such as: geographical asynchronous replication, online add node, online backup, NDBINFO for improved monitoring and the Win32 port.