MySQL Storage Engines - which do you use? TokuDB? MyRocks? InnoDB?
The MySQL storage engine landscape is wide and varied (and for a very long time, it was the only database server to support this concept) - it started with MyISAM, and it became a solid database with the popular and default InnoDB storage engine. However there are many contenders and depending on the type of use case you might benefit from TokuDB or MyRocks, engines that are included in Percona Server for MySQL. Learn when to use the right engine for the job.
Principal Technical Services Engineer, Percona
Sveta Smirnova works as MySQL Support engineer since year 2006, she is also author of book "MySQL Troubleshooting" and author of JSON UDF functions for MySQL. In years 2006 - 2015 she worked in in Bugs Analysis MySQL Support Group in MySQL AB, then Sun, then Oracle. In March 2015 Sveta joined Support Team in Percona. In years 2012-2015 she worked on bugs priority. She was also Support representative in MySQL Backup Development Team. She works on tricky support issues and MySQL software bugs on a daily basis. Before starting at MySQL in 2006, she worked as web developer on several closed CRM systems. In years 2012-2015 she worked on MySQL Labs project "JSON UDFs for MySQL". She is active participant in the open source community. Her main interests in recent years is solving DBA problems, finding ways to semi-automate this process and effective backup techniques. Sveta is author of the book "MySQL Troubleshooting" (http://shop.oreilly.com/product/0636920021964.do)