In order to answer you first question we would need to know what types of data you plan on storing and latency requirements. If it is semistructured/unstructured data then HBase *can* be a great fit but I have seen very few cases where you will want to scrap your RDBMS completely. Most organizations that use HBase will still have a need for a RDBMS/MPP solution for real time access to structured data.
Matt -----Original Message----- From: Jignesh Patel [mailto:[email protected]] Sent: Tuesday, September 20, 2011 4:25 PM To: [email protected] Subject: Re: Using HBase for real time transaction Tom, Let me reword: can HBase be used as a transactional database(i.e. in replacement of mysql)? The requirement is to have real time read and write operations. I mean as soon as data is written the user should see the data(Here data should be written in Hbase). -Jignesh On Sep 20, 2011, at 5:11 PM, Tom Deutsch wrote: > Real-time means different things to different people. Can you share your > latency requirements from the time the data is generated to when it needs > to be consumed, or how you are thinking of using Hbase in the overall > flow? > > ------------------------------------------------ > Tom Deutsch > Program Director > CTO Office: Information Management > Hadoop Product Manager / Customer Exec > IBM > 3565 Harbor Blvd > Costa Mesa, CA 92626-1420 > [email protected] > > > > > Jignesh Patel <[email protected]> > 09/20/2011 12:57 PM > Please respond to > [email protected] > > > To > [email protected] > cc > > Subject > Using HBase for real time transaction > > > > > > > We are exploring possibility of using HBase for the real time > transactions. Is that possible? > > -Jignesh > This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. The information contained in this email may be subject to the export control laws and regulations of the United States, potentially including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this information you are obligated to comply with all applicable U.S. export laws and regulations.
