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 need to implement a massive databse with a relatively simple structure. That is few tables, no complex dependencies, etc. How would I begin to choose between say Cassandra and CouchDB?
Well it really comes down to how you want your data to be stored and how you access it. It also depends on how you want to shard your data and if you want failover/replication.
CouchDB is really good as a document database and has a nice RESTful interface to access everything. It is a multiversion store so updating a record creates a new version everytime it is stored.
Searching CouchDB is done by writing a query in JavaScript to search for what you want.
Cassandra on the other hand is a column database and needs you to use the Thrift API to insert/update and delete the data. It is very good in that it has a caching layer that is disk backed.
Like I said, work out how you want to use your data then start looking at all the different things.