There is no one magic solution to having MySQL As A Service work well, it's a lot of small moving parts and options that need to be set, monitored and configured. We may wish it was different, or look at other database technologies, but there is a lot of legacy code that talks to MySQL, with all it's idiosyncrasies - and we need to be able to support this code.

In this talk, we'll cover many of the problem areas and what you can do to avoid them. We'll cover stock Oracle MySQL, Percona Server and MariaDB. Where suited, Drizzle will also be discussed.

A key focus area will be how to run MySQL As A Service. This makes sense even in smaller organisations, providing database services to various apps, not just in big cloud providers.

Some areas we'll examine:
- IOPs
IOPS are eaten by database sytems for breakfast, MySQL is no exception. We'll look at a crash safe server with replication, how many fsync()s a single transaction causes (hint: greater than 1) and how that number can be reduced.

- ENOSPC
MySQL traditionally handles ENOSPC very, very poorly. We'll look at new features we've implemented to help avoid ENOSPC. This includes replication logs, UNDO logs and temporary files.

- Flexibility in users/admin
We'll also cover ways to provide users with the root MySQL user while not giving them access to the underlying Virtual Machine - enabling a more standardized Database As A Service platform yet giving users a lot of flexibility in how they use their database.

- Backup/restore/spawning slaves
Backup and restore is also integral to a good database server, so we'll examine backup options that work for streaming directly into cloud storage rather than local disk.