Tell me more ×
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.
up vote -2 down vote favorite

Can anyone help me to make right decision for choosing scalable and reliable database?

I have to create 3-4 tables with around 200 columns each and these tables will have around 5000 data records. As per requirement, what should I use from MongoDB and MySQL?

Can you please compare these also?

share|improve this question
I have to store around 5000 records in that tables – RAJ ... Aug 30 '12 at 7:33
Choose the one which you know how to use. This amount of data is far from being restrictive. 200 columns per table sound strange, however, but your use case may require that. – dezso Aug 30 '12 at 8:11
@dezso I know usage of both but thanks for suggestion, can you please describe pros & cons mysql vs mongodb? – RAJ ... Aug 30 '12 at 8:17
2  
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 Travers Aug 30 '12 at 10:20
hmm... anyways, thanx for responses – RAJ ... Aug 30 '12 at 10:36
show 2 more comments

1 Answer

up vote 6 down vote accepted

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:

  1. If you need ad hoc reporting go with an RDBMS
  2. 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.
  3. 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.
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.