Blog

Published by John Potocny, Ewen Fortune, and Alex Slotnick on Sep 6, 2017 11:02:05 AM

The Basics of Sharding in MongoDB

Sharding is a mechanism widely used in today's most popular database systems, an effective way to divide, categorize, and organize data into manageable chunks. In some database types, such as MySQL, the use of sharding is an architectural decision, while in other databases, such as MongoDB, sharding is a fully supported, native feature. If effectively used, it can play a role in scaling a system effectively to meet organizational or business demands.

Read More
Published by John Potocny and Ewen Fortune on Jul 24, 2017 12:31:35 PM

Deciding Which Storage Engine is Right for You: WiredTiger

We've recently written several articles about the history and advantages of MongoDB's storage engines, explaining why WiredTiger replaced MMAPv1 as the default engine and the contexts in which MMAPv1 might still be the best choice for some users.

In this article, we'll continue these conversations and consider how you should decide which storage engine is right for you, this time returning to WiredTiger. It may be MongoDB's default engine, but is it the best option in every situation?

Read More
Published by John Potocny and Ewen Fortune on Jul 6, 2017 7:43:12 PM

What is MongoDB's _id Field and How to Use It

MongoDB's users are well known for valuing the database's capacity for growth. After all, the system's tagline is "for giant ideas," and for good reason.  The system supports extreme scalability and has been designed to store exceptionally large numbers of documents. Among all the data that a MongoDB system handles, however, there's only one field that exists across every document: the _id field.

Read More
Published by John Potocny and Ewen Fortune on Jun 23, 2017 6:08:47 PM

Deciding Which Storage Engine is Right for You: MMAPv1

In a recent article, we began an examination of MongoDB storage engines by explaining why WiredTiger is the current default engine. In this piece, we'll continue discussing storage engines and start to look at the specific characteristics of other available options, beginning with MMAPv1, to help readers understand which one is right for their system and workloads.

Read More
Published by John Potocny and Ewen Fortune on Jun 19, 2017 5:51:49 PM

When to Use explain() in MongoDB

In MongoDB, the command db.collection.explain() is an important operation that can help you understand exactly how your queries execute and behave. Once you have a grasp of how MongoDB handles explain(), using it lets you examine queries in a number of ways.

Read More
Published by John Potocny and Ewen Fortune on Jun 14, 2017 11:43:05 AM

Why WiredTiger is the Default MongoDB Storage Engine

Last week, when we published our blog post about working-sets in MongoDB, one of our colleagues told us that he'd been aware that MMAPv1 had previously been MongoDB's default storage engine, but he didn't know why WiredTiger had since taken its place. We saw this as an opportunity to write a follow-up post to explain some of the contrasts between the two and explore the advantages of WiredTiger, which (we think) led MongoDB to making it the system's default storage engine.

Read More

Subscribe to Email Updates

Posts by Topic

see all