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.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are in the process of putting together a whole system for a new startup company. This project is meant to store thousands of requests and each one needs to be stored and displayed in real-time.

This data will then be analysed so as to gather insight on traffic patterns etc.

After conducting a good amount of research we thought that HBase would be a perfect fit due to its HDFS replication, MapReduce via Hadoop and fast read/write mechanism. However the issue is that it is recommended to have a couple of million rows when implementing Hbase for the first time.

Obviously being a startup we would not have such traffic in the beginning however the number of requests is expected to increase quite quickly over a short period of time.

Therefore what would you suggest, still going for HBase or starting with e.g. MySQL and change once we have the right amount of traffic? The issue with using MySQL or any other DBMS is the aspect of real-time whilst also having to shift the whole system over to HBase should we start running into issues of sharding etc.

share|improve this question

closed as off-topic by Mark Storey-Smith, Marian, Max Vernon, Michael - sqlbot, RolandoMySQLDBA Oct 18 '13 at 23:39

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Shopping list question - questions about which tool, library, product or resource you should use are off-topic here because they quickly become obsolete and often are just about the preferences of the answerer. If you have an issue with or a question about a specific tool, please revise your question to conform to that scope." – Mark Storey-Smith, Marian, Max Vernon, Michael - sqlbot, RolandoMySQLDBA
If this question can be reworded to fit the rules in the help center, please edit the question.

NoSQL and RDBMS are totally different animals. You should pick the one which suits your data and how you intend to record and access it.

Don't pick your style of database system on the grounds of performance. Performance can be managed in a range. If HBase isn't performant at your start up volumes, then maybe you'll just have to work harder to tune it, or throw more money at hardware, or just live with slightly lower performance until your volumes catch up to HBase's sweet spot.

share|improve this answer

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