Good NoSQL database for Write-Read Intensive Site

3
votes

Ok I do have a small messaging site for my client. Well its more likely a post-comment system(created in PHP). Now my client want a system that can comment to another existing comment and add some features like liking and tagging. Another thing is the existing system is heavily used by my client in his company as they use it like a skype chat(that makes it write-read intensive). well my client want's to use open source software as possible. so I used mysql community edition.

Too much about my story... So I had a 1 week research about NoSql databases and I found it right for my requirements as my client wants to add features (that means adding and adding columns and tables from time to time.) Now these are nosql database systems that caught my eye.(well if you can suggest other nosql database system its ok)

  1. MongoDB
  2. CouchDB
  3. Redis

Now my question is which of the three is good for my situation? I also read some bad things about those 3 nosql databases

  1. MongoDB is crappy on its 2.x version
  2. CouchDB is slow (my client doesn't want slow)
  3. Redis is memory-based so it just writes on the disk on certain intervals. so when the system crash in the middle of the interval then the data is lost

I want to have some opinions about this and any advice that can help me to cope up with my upcoming situation

1
phpdatabasenosql
Based on the information you give you do have knowledge about relational databases and not about NoSQL databases. Now this isn't a case which is not doable in a relational database which you already have for the system I would strongly consider using the relational database you already have. Setting up NoSQL directly for a client and developing a company critical application doesn't feel like the right path for your project. First get the knowledge and experience before deploying it to a client project is my opinion. - Luc Franken
@LucFranken yeah but what im worrying about is the comment-comment system. well it will make my rows reference and reference to each other... anyways thank you for your nice answer - Netorica
Yes, you might be totally right from a technical perspective but also consider the business side of the case since that will be the customer experience, not the technical choices. - Luc Franken

1 Answers

2
votes

MongoDB is a popular solution to this, and my personal preference. The great thing about Mongo (besides being schemaless) is that you can have nested/embedded documents. So for example, you can have a comment which has an array of sub-comments which each have their own arrays of sub-comments. I don't know of any other datastore that has that feature. It's also fast.

CouchDB has some nice features, but Mongo is so similar and much better.

Redis is very different from the other two. It's used mostly as an alternative to memcached. So it's primarily used for temporary data. Although it has some nice pubsub features built in. A lot of people use both MongoDB and Redis, but for different things.