01 Apr '12, 9am

Why I think Mongo is to Databases what Rails was to Frameworks // RailsTips by John Nunemaker

I have been using mongo and MM for a project the last few months. I was initially very enthusiastic but as my data model has gotten more complex, I struggled to map it to the mongo way of thinking. Mongo does not do joins, so you are encouraged to store things hierarchically. So if I have a site with departments, and departments have products. The department can contain all the products, which might be nice for showing a department page which lists the products – 1 trip to the database. But to show a product page, guess what – you have to load the entire department again. And if products are in multiple departments, you have to make products a top level collection and then you’re doing multiple trips to the database to fetch them all for your product list page. I am having doubts now that document-oriented databases and web applications are a good match. Has anyone else st...

Full article: http://railstips.org/blog/archives/2009/12/18/why-i-think...

Tweets

Check out what we think irresponsible when it c...

emmagem.com 01 Apr '12, 3am

BEAT PERCUSSION GROUP “RHYTHM II — Mar 31, 2012 8:30pm - Apr 1, 2012 3:00pm With the critically acclaimed “Rhythm – Percus...

Walken on Rails

rubyflow.com 01 Apr '12, 8pm

Walken on Rails Posted by laserlemon on April 01, 2012 — 1 comment For quite a while now, Collective Idea has been working...

@artolamola dar una respuesta valida para todos...

blog.headius.com 01 Apr '12, 11am

There's been a little bit of buzz about David Heinemeier Hansson's announcement that Josh Peek has joined Rails core and i...