Running MongoDB in Production Part 2

Are you a seasoned MySQL DBA that needs to add MongoDB to your skills? Are you used to managing a small environment that runs well, but want to know what you might not know yet?
MongoDB works well, but when it has issues, the number one question is "where should I go to solve a problem?"

This tutorial will cover:
Architecture and High-Availability

Replication Best Practices
Using read and write concerns
Disaster Recovery Considerations

Hardware

MongoDB Hardware Themes
Storage recommendations
System CPU considerations
Network Architecture

Tuning MongoDB

Storage Engines
Durability
What not to enable

Tuning Linux

Kernel Tuning Best Practices
Filesystem and Disk Recommendations
Virtual Memory Recommendations
Deployment Best Practices

Download Slides

About the Author

Timothy Vaillancourt

Tim joined Percona in 2016 as Sr. Technical Operations Architect for MongoDB with a goal to make the operations of MongoDB as smooth as possible. With experience operating infrastructures in industries such as government, online marketing/publishing, SaaS and gaming combined with experience tuning systems from the hard disk all the way up to the end-user, Tim has spent time in nearly every area of the modern IT stack with many lessons learned. Tim is based in Amsterdam, NL and enjoys traveling, coding and music. Prior to Percona Tim was the Lead MySQL DBA of Electronic Arts' DICE studios, helping some of the largest games in the world (“Battlefield" series, “Mirrors Edge” series, “Star Wars: Battlefront”) launch and operate smoothly while also leading the automation of MongoDB deployments for EA systems. Before the role of DBA at EA's DICE studio, Tim served as a subject matter expert in NoSQL databases, queues and search on the Online Operations team at EA SPORTS. Prior to moving to the gaming industry, Tim served as a Database/Systems Admin operating a large MySQL-based SaaS infrastructure at AbeBooks/Amazon Inc.