This post originated from an RSS feed registered with Java Buzz
by News Manager.
Original Post: How to screw up your MongoDB schema design
Feed Title: JavaWorld
Feed URL: http://www.javaworld.com/index.rss
Feed Description: JavaWorld.com: Fueling Innovation
Tonight I'm going to a sold-out MongoDB event hosted by my company at our local startup incubator. Already, 250 have people signed up. That's a pretty good crowd for Durham, NC, but not surprising considering the focus is MongoDB schema design.
Schema design with MongoDB is almost too easy, but if you've been flattening things out into tables for 20 years, it may seem hard. If you create Mongo entities that are a 1:1 port of equivalent items in your RDBMS, you'll be sorely disappointed by MongoDB's performance, consistency, and so on.
On the Web, you'll find plenty of negative opinions about the quality of MongoDB. You'll also come across rave reviews and glowing recommendations. I'm willing to bet that the difference between thumbs-up and thumbs-down in 99 percent of those cases is whether the schema was or was not appropriate for a document database.