MongoDB Engines: Demystified
In MongoDB you normally have the choice of WiredTiger or MMAPv1, and with Percona Server we have added two more engines( MongoRocks and In Memory). How do you know which to use? How do you know which to tell developers to not use. How do these affect how you might design you data access functions and your schema? This are all areas we will touch on to help make sure you're picking the right engine for your workload, and in some cases help you realize some data shards should have different engines.
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)