Why do people keep thinking of MySQL as a good RDBMS? I'd recommend looking at IDS (Informix Dynamic Server) now part of IBM. They've changed their licensing around a bit and there are some "free" options. (You have to look at the licensing based on platform and your use case)
The real reason that makes IDS interesting is that it has better ER and extensibility than any other database. (Lowest TCO too. Just ask a certain retailer located in the Midwest. ;-) Hadoop/HBase as part of some analytics to push/pull data from IDS makes a lot of sense. Sorry for my mini-rant. -Mike > Date: Wed, 7 Jul 2010 13:13:28 -0700 > From: [email protected] > Subject: Re: Whether by applying HBase, an application still needs RDBMS? > To: [email protected] > > > > 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 > _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
