Scaling with MongoDB

Here is the video from Kristina Chodorow's O'Reilly webcast Scaling with MongoDB. The webcast focused on MongoDB's sharding functionality and how it allows MongoDB to scale horizontally. In addition, the webcast focused on replica sets and how they enable automatic failover and recovery of database nodes.

Click to read more ...

MongoDB Crash Recovery

In Kristina Chodorow, software engineer at 10gen, latest post she walks us through several recovery scenarios that could occur while using MongoDB. Of course, a straight list would boring... but choose your own adventure, how could you resist.

Click to read more ...

Scaling with MongoDB Webcast

Kristina Chodorow, software engineer at 10gen, will be discussing how to scale with MongoDB this Friday (9/17) at 10am PST.

Full description of the webcast:

MongoDB's architecture features built-in support for horizontal scalability, and high availability through replica sets. Auto-sharding allows users to easily distribute data across many nodes. Replica sets enable automatic failover and recovery of database nodes within or across data centers. This webcast will provide an introduction to scaling with MongoDB by one of the developers working on the project.

For those who need reminders follow us on Twitter or Facebook, we'll send out a reminder on Friday morning 6am PST.

Sign up for the webcast here: Scaling with MongoDB

Performance tweaks for MongoDB

Kristina Chodorow has a post where she discusses a few tweaks you can make to your code to improve performance in MongoDB.

Some of the recommendations at a high level are basic, such as the recommendation to not waste any connections. However, there are some pretty interesting side effects with the PHP connection code.

$connection = new Mongo();
$connection->connect();

In the previous code it appears the user wants to create a new connection. However, under the hood the following is happening:

1. The constructor connects to the database.
2. connect() sees that you’re already connected, assumes you want to reset the connection.
3. Disconnects from the database.
4. Connects again.

The result is that you have doubled your execution time. This is just one example of many that Kristina provides. If you are using MongoDB I'd suggest you check it out.

Read more: Oh, the Mistakes I've Seen