News for hackers. Stuff that matters.
Re:Scaling with MongoDB (or how Urban Airship abandoned it f... by schmichael on Wednesday June 22, 2011 @09:05PM (#2686173)
You're basically implementing an optimized version of ObjectId for your use case and having to take a couple stabs at it as well. No big deal, but there are just lots of little tricks like that to learn with MongoDB.

"My stuff wouldn't work on PostgreSQL at all, I have so much data that I must use sharding."

We had to implement sharding as well and chose to do it manually in PostgreSQL. Luckily our schema made that relatively easy and natural. YMMV

Re:Scaling with MongoDB (or how Urban Airship abandoned it f... by bdarfler on Thursday June 23, 2011 @09:28AM (#2687745)
As mathias_10gen points out below this is the default behavior of ObjectId. You just have to be carful if you decide to override the _id field.
Re:Scaling with MongoDB (or how Urban Airship abandoned it f... by FooBarWidget on Thursday June 23, 2011 @10:47AM (#2688033)
It isn't just the _id field, it's any indexed field.