> From: Jean-Daniel Cryans <[email protected]> > Also, about using any other DBMS in conjunction with HBase, I would > simply recommend using the right tool for the right job.
This seems like a sensible approach to me. We are using HBase for the data that needs massive scalability, but are using a standard RDBMS (MySQL) for most of our needs. The RDBMS is perfectly capable of handling reasonably large data sets...just not the truly massive ones. MySQL has more/better developed tools, supports convenient features like indexes and triggers, and is much easier to deal with, administer, etc. It is currently faster to develop and easier to find people who know the technology. So we default to using RDBMS, but use HBase for data structures where we know we'll exceed RDBMS capabilities. But I'm curious what other people think as well...anyone? Do you use HBase for your whole app? Or do you have a hybrid approach? Neal
