Re:Scaling with MongoDB (or how Urban Airship abandoned it f...
by schmichael on Wednesday June 22, 2011 @07:43PM
(#2685937)
Everyone should be upvoting this.
I vaguely remember 10gen brainstorming some ideas for fixing this, but it's a pretty poor design decision for a database you're advertising for use in "Big Data" scenarios. (Not that our measly 120 GB db constitutes big data... but even at Medium Data something as silly as key sizes can have a significant performance impact).
Re:Scaling with MongoDB (or how Urban Airship abandoned it f...
by bdarfler on Thursday June 23, 2011 @09:33AM
(#2687757)
Some/M=most Mongodb client libraries can do this for you. I can see arguments both ways to keep it in the server or keep it in the client library. 10gen does a hell of a job supporting a wide variety of very good client libraries.
When you're a database in 2011 then you should have a damn good reason for asking programmers to space-optimize their identifiers. I can't see such a reason in Mongo really.