I’m looking at using CouchDB for one project and the GAE app engine datastore in the other. For relational stuff I tend to use postgres, although I much prefer an ORM.
Anyway, what use cases suit non relational datastores best?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m looking at using CouchDB for one project and the GAE app engine datastore in the other. For relational stuff I tend to use postgres, although I much prefer an ORM.
Anyway, what use cases suit non relational datastores best?
Here is a nice little article (spread over three pages) that covers the use-case for non-relational databases.
http://www.readwriteweb.com/enterprise/2009/02/is-the-relational-database-doomed.php
In a nutshell, when you need massive scalability then you probably need a non-realtional db. Of course, you may well end up writing a lot more code to do what a relational db does for you, but if you really need that scalability, then the relational db option is usually more expensive, and very tricky to architect properly.