> I think there has to be some clarification. > > The OP was asking about a mySQL replacement. > HBase will never be a RDBMS replacement. No Transactions means no way of > doing OLTP. > Its the wrong tool for that type of work.
Agreed, if you are looking to handle relational data in a relational fashion, might be better to look elsewhere > Recognize what HBase is and what it is not. Not sure what you're referring to here. > This doesn't mean you can't take in or deliver data in real time, it can. > So if you want to use it in a real time manner, sure. Note that like with > other databases, you will have to do some work to handle real time data. > I guess you would have to provide a specific use case on what you want to > achieve in order to know if its a good fit. He says: >> 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). Row mutations in HBase are seen by the user as soon as they are done, atomicity is guaranteed at the row level, which seems to satisfy his requirement. If multi-row transactions are needed then I agree HBase might not be what he wants. J-D
