Here are some of our stats of FB messages on HBase: 6B+ messages/day
Traffic to HBase 75+ Billion R+W ops/day At peak: 1.5M ops/sec ~ 55% Read vs. 45% Write ops Avg write op inserts ~16 records across multiple column families and column family updates in the same record are atomic (inside the same transaction) -dhruba On Thu, Jan 12, 2012 at 6:50 AM, fullysane <[email protected]> wrote: > > Hi Mike: > > Thereason I am thinking Hbase for OLTP is that I need a column-based > (key-value pair)OLTP DBMS which allows me not to predefine columns for a > table and can add new column to a table on the fly like Hbase does. Alougth > this can be done in any RDBMS with so called skinny and tall table contain > only key and value columns and then pivoting the data to look like a > traditionla spead sheet like table, but the pivoting perforamnce will be a > drag for query. > > Any idea to solve this problem? > > Thanks, > > > > > fullysane wrote: > > > > Hi > > > > I know HBase is designed for OLAP, query intensive type of applications. > > But I like the flexibility feature of its column-base architecture which > > allows me having no need to predefine every column of a table and I can > > dynamically add new column with value in my OLTP application code and > > capture its meta data information. > > > > My question is basically about if we can use HBase for OLTP application > > database. I know Hbase works well with Inserting column data of a row key > > and set new version for the new piece of the data, and not so well for > > updating and deleting existing piece of data. However, if I turn OLTP > > update and delete operations into all insertion of new version of colum > > data as I described below: > > For OLTP data update, if I set my table column family’s versioning to 1 > > and always do insert (put) when there is need to update an existing data > > row columns, and let Hbase to handle the delete of the old versions > > through DB garbage collection. > > For OLTP data delete, I can use inserting new version on a flag field to > > “deleted”, which is a logical delete, and have some batch job to clean up > > all logically deleted rows later. > > > > Will the above scenario work for using HBase for an OLTP application? Any > > flaws on doing it? > > > > Can some one share the experiences of using HBase for OLTP applications? > > > > Thanks, > > > > > > -- > View this message in context: > http://old.nabble.com/Question-about-HBase-for-OLTP-tp33107782p33128226.html > Sent from the HBase User mailing list archive at Nabble.com. > > -- Subscribe to my posts at http://www.facebook.com/dhruba
