Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Josue Del Cid
6,292 PointsRoR with mongo db
Any one knows a good tutorial to start with rails with mongo db??
7 Answers
Gareth Redfern
36,217 PointsTuts+ have just published a Mongo db course, I am not sure if they use Rails with it.
James Barnett
39,199 Points@Josue - Any particular reason you are interested in using rails with Mongo DB?
Josue Del Cid
6,292 PointsThanks @Gareth i will check it out!... @James.. well i'm starting to learn rails but i want to start learning with mongo DB.. that's the reason..
James Barnett
39,199 PointsMongoDB solves some very particular problems, such as for a website that has 5 million daily views.
Here's an interesting take on the pro's and con's of scalability of NoSQL vs relational databases.
First learn SQL and the relational paradigm.
SQL represents 40 years of experience designing general data stores that work for the widest set of applications. SQL databases solve many very hard problems which you are probably not aware of.
If you jump into NoSQL first you will be implementing SQL features in your application code, and doing a shitty job of it because you have experience with data stores that actually solve these problems well.
The reason for the existence of so many NoSQL databases is the rise of web applications and the need to scale massively. However the majority of apps will never need to scale beyond a single well-tuned database server anyway. By the time they do you will have had problems to solve regardless of what data store you used.
The advantage of SQL is that it's a fantastic hedge on the evolution of your data usage patterns because it is designed to support ad-hoc queries well, and the schema prevents bad application code from trusting your data into chaos at the first occurrence of a small bug.
Realistically if you knew you had to build an app for 5 million daily users, and you knew exactly what it was going to do, then an SQL database very well might be the wrong choice.
But in the real world you have a long road ahead before you hit that scale, and you'll have real data to determine what kind of alternate data stores can best handle your load. Personally I'm a huge fan of redis, and its ability to scrape bottlenecks off a MySQL database in a piecemeal fashion.
Damian Tommasino
96 PointsMongoDB and other NoSQL databases are great when used properly. The best use cases for these are transaction style operations, logs, or chats.
Rodrigo Muñoz
Courses Plus Student 20,171 Points@James - Thank you for that info. It helps a lot.
James Barnett
39,199 Points@Rodrigo - You are very welcome.
I agree with @Damian, for sites that have massive millions of entries per day in their transactional data, NoSQL can be a good choice.