Is Cassandra comparable to HBase?
HBase is known as keystore and random read with key-based .get and .put functions. Is Cassandra the best choice for meeting key storage requirements? Can it support key-based random reads? If so, under what conditions should I choose Cassandra over HBase in a Spark Streaming application?
source to share
Cassandra - The Best Choice To Meet Key Value Store Requirements?
Yes, this is one of the good options.
-
Cassandra has a decentralized architecture. Any node can perform any operation. It provides AP (accessibility, separation-tolerance) by the CAP theorem.
-
With time
Can it support key-based random reads?
Yes.
If so, under what conditions should I choose Cassandra over HBase in Spark Streaming App?
Both HBASE and CASSANDRA can be used for streaming applications. The natural choice for CASSANDRA is its high availability.
Title question: Is Cassandra comparable to HBase?
see below for more details ...
CAP_theorem
- Consistency (all nodes see the same data at the same time)
- Availability (ensuring that every request gets a response as to whether it was successful or not)
- Separation tolerance (the system continues to operate despite an arbitrary loss of message or a failure of part of the system)
Conclusion : CASSANDRA supports AP if you are looking for you can continue with CASSANDRA
Note. According to the CAP theorem, a distributed CANT system satisfies all three of these guarantees at the same time.
source to share