Just over a month ago, I presented on storing stats in MongoDB at MongoChi 2011. 10Gen posted the video recently, so I thought I would share it here. The first 5 minutes or so are a bit rough, but it improves after that. I’ll be presenting the same thing at MongoSV next week if you want to catch it live.

I’ve also embedded the slides below.

Interesting post on the Boxed Ice blog about how they are using MongoDB capped collections for a queue system.

Until today I did not realize you could index a capped collection. Not sure why I was confused about that, but now I totally understand how capped collections would work great for a queue.

For those that follow me here, but not over at RailsTips, I recently released a new post on storing stats in MongoDB. The topic of this post is around storing large ranges of data.

Yesterday, MongoDB 2.0 was released. Personally, I am excited about the concurrency improvements and the more compact index storage. Also, for the haters, journaling is now on by default. Great release!

Over at RailsTips, I posted on how I use a single document to store a lot of good stuff in Gaug.es, the real-time stat app we are making at Ordered List.

Sometimes I think all I do is link to Kristina, but she has written several great posts, so enjoy another.

MongoHQ has raised $417K from a few investment firms to help grow the service.

In depth post on how Mongo’s geo spatial indexing works.

Mongoose, the MongoDB object modeling tool for node.js that powers LearnBoost, just hit 1.0.

Map/reduce output has changed in 1.7.5 (and thus on up). This post does a great job explaining why temporary collections are no longer an option and how to use map/reduce with the updates.

The MongoDB team has released 1.7.5 (unstable) which includes single server durability. Using the —dur option when on start turns on journaling. The documentation on journaling is also a good read.

Kristina Chodorow posts about why the command helpers are harmful and what you should be doing instead.

Every command helper is just a find() in disguise! This means you can do (almost) anything with a database command that you could with a query.

Boxed ice’s third post in a series of six covers how to get information out of MongoDB using the server status command. If you are curious about how to do this from the Ruby driver, I mention how in a post about some Mongo Scout Plugins I created.

Ethan Gunderson has posted a good introduction to the Mongo ruby driver. The article includes a bit on connecting, inserting, updating, and indexing.

Five slick new features have been added to replica sets, including initial sync from secondary, slave delay, hidden, freeze a member, and fast sync. This post has a few paragraphs detailing each.

ServerDensity, who already provides some MongoDB monitoring, is working on a new dedicated MongoDB monitoring solution. They already have my email for when they launch. :)

Another post by BoxedIce on why RAM is so important with MongoDB.