Cassandra/HBase or just MySQL: Potential problems doing the next thing
Posted
by alexeypro
on Stack Overflow
See other posts from Stack Overflow
or by alexeypro
Published on 2010-03-26T20:47:07Z
Indexed on
2010/03/28
0:53 UTC
Read the original article
Hit count: 525
Say I have "user". It's the key. And I need to keep "user count". I am planning to have record with key "user" and value "0" to "9999+ ;-)" (as many as I'll have).
What problems I will drive in if I use Cassandra, HBase or MySQL for that? Say, I have thousand of new updates to this "user" key, where I need to increment the value. Am I in trouble? Locked for writes? Any other way of doing that?
Why this is done -- there will be a lot of "user"-like keys. Different other cases. But the idea is the same. Why keep it this way -- because I'll have more reads, so I can always get "counted value" very fast.
© Stack Overflow or respective owner
