Caching your application data with MySQL and TokuDB
Even if InnoDB is universally recognized by DBAs as "the" engine to use for production data, there are use cases where InnoDB just does not fit. In this talk we will introduce the most popular engines available for MySQL to date, focusing on the limitations that plague InnoDB when it's about inserting rows at high rate and/or using a random primary key, like an UUID. We will describe how we worked around this limitations by using the TokuDB engine, first showcasing advantages of TokuDB versus InnoDB in terms of write performance. From there, we will show you how we are using MySQL and TokuDB together as an high performance application cache, with random keys and opaque/BLOB values, in fact using MySQL as a key-value based persisting cache system. We will walk you through our configuration file, schema definition, sample queries, and how we use partitioning to expire old data from the cache.
Andrea joined 2 years ago Lastminute.com Group as MySQL Database Administrator. He has 10+ years of working experience on MySQL world after a short period as a PHP developer. He holds a master’s degree from Pisa University, Italy in computer science.
Sr. MySQL DBA & DBA Team Lead, Lastminute.com
I have been always interested in MySQL since the early days of v3.23. After spending 20+ years in the IT field, mostly as a system administrator, In the last few years I decided to focus exclusively on MySQL, and have been working as full time MySQL DBA since. Since 2014 I am leading the MySQL DBA Team at lastminute.com .