Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Raj: The problem is that the two are so different that you really can't come up with simple pros and cons. It really depends on how each one matches your use case. We simply don't have enough info to give you anything reasonable other than more questions.
–
Chris TraversAug 30 '12 at 10:20

1 Answer
1

I think your first question needs to be relational or non-relational. This depends on what you are doing etc. However your tradeoff is that relational databases (including MySQL in traditional mode) will be relatively rigid with data coming in, but are very flexible with data output. NoSQL databases generally (and Mongo is this way) are very flexible with data input, but not flexible at all with data output. This means:

If you need ad hoc reporting go with an RDBMS

if your data is very flexible and not subject to mathematical transformation, you may benefit from Mongo more than you will if it is subject to such transformation.

You are highly unlikely to reach a point where your db is your scaling bottleneck. If you do there are solutions there on both sides.