I'm not experienced with NoSQL, but one person on my team is calling for its use. I believe our data and its usage isn't optimal for a NoSQL implementation.

However, my understanding is based off reading various threads on various websties. I'd like to get some stronger evidence as to who's correct.

My question is therefore, "Is there a technique for estimating the performance and requirements of a certain database, that I could use to confirm or modify my intuitions?".

Is there, for example, a good book for calculating the performance of equivalent MongoDB/MySQL schema?

Is the only really reliable option to build the whole thing and take metrics?

closed as not constructive by Greg Askew, MadHatter, Zoredache, mdpc, Ward Nov 14 '12 at 17:20

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Rather than building the whole thing, I would suggest that 2 people (or 2 teams) spend a week investigating 2 competing options, build a small prototype and then decide. Don't make performance the deciding factor, but rather ease of coding and maturity of the tools you would end up using, from the developer to the sysadmin. – Sebastiano Pilla Nov 14 '12 at 14:57

I'm not aware of any kind of rigorous method to choose between a NoSQL or a RDBMS, but I find information in this stackoverflow post pretty interesting:


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