I believe that their are lots of NoSql overview slide decks that give
great intro to the why. For me:
Performant writes
Dreaming of master master master......
Time series data schemas
Batch processing of data via hadoop
Replication can't keep up
Spending r&d time on hacking work arounds to mysql rather than product
development.
You already gave master drbd master and 3 or more slaves.
Thanks;
Wade Arnold
On Mar 17, 2010, at 6:34 PM, "eltonsky" <eltont9...@hotmail.com> wrote:
Hello everyone,
I read through some literature and end up with some ideas on HBase and
RDBMS. Please correct me if I am wrong:
* Use HBase if the application is going to handle large datasets, like
Petabytes. That means when scalability is a big concern; Also,
because HDFS
replicates data autoamtically, we have reliability;
* Correspondingly, we can just use RDBMS when the dataset is not
huge enough
to worry about scalability often. Because anyway, RDBMS has more
functionalities we can take advantage of, e.g. secondary indexing,
referential integrity.
Is the above right?
Regards,
Elton
--
View this message in context:
http://old.nabble.com/When-should-I-jump-on-HBase-rather-than-RDBMS--tp27939881p27939881.html
Sent from the HBase User mailing list archive at Nabble.com.
