ruby on rails - Mongodb: What to know before using? -

I am starting a hobby (non-revenue) project using rubies on tracks. I have done a fair amount of development in Rail Rail using PostGrussle, and I can make a very good copy of the generalized schema. However, what is better for something new than a hobby project that looks prominent and new to the Mongergod?

When you start using Mongodb, what techniques did you write later, which tells you, "If only I knew when I started!" Did the plug-in know that you have used it since the beginning, if you are known only? You will definitely be the second to recommend MongoMapper, if you want to 'bookmark again.' Then going to use MongoDB with railways. I warn you, however, there are no documents (yet) in addition to some blog posts, if you are not excavating in the source code, to see how things work, it is not for you yet .

If you are working outside the railroad, then I would advise to stay away from the Mongomapper. Since it expects MongoDBee from SQL enabled ORM, similarly it is working in some way, it does not give you a good idea of ​​the different thinking power behind MongoDB.

The second thing I would recommend, especially when you want to know how to make the schema normal, then no to think about MongoDB as a database for now The way you organize your data into MongoDB is very different which is with a relational database. Try to think more about the place to store and retrieve Ruby hash. You can do some relational things with MongoDB, but I only recommend to paste it with the documents contained in it. Trying to wrap around.

The link you should look at, I recommend reading as much as you can on the mongodb site. Have a look at their documentation especially, especially, and to get the idea of ​​certain specific advantages and powers of a NoSQL database.