13 Sep '13, 9pm

Interesting reading: Why I think Mongo is to Databases what Rails was to Frameworks

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://www.railstips.org/blog/archives/2009/12/18/why-i-t...

Tweets

#rails good piece of the API to be aware of

api.rubyonrails.org 15 Sep '13, 10am

Optimistic locking allows multiple users to access the same record for edits, and assumes a minimum of conflicts with the ...

Rails: Think small

rubyflow.com 09 Sep '13, 2pm

Rails: Think small Posted by ior3k on September 09, 2013 — 0 comments I just wrote an article discussing ways to reduce th...

Think slave free chocolate - think Fairtrade.

ethicalsuperstore.com 14 Sep '13, 2pm

The story of Divine starts back in 1993 with the birth of Kuapa Kokoo, a pioneering cocoa farmers’ cooperative in Ghana, d...