I definitely can’t use it. Cassandra conducts core banking transactions because C* is slightly inconsistent.
But Cassandra writes very fast, which is good for OLTP.
I can use C* for OLAP because it is very fast to read, which is also for reporting Useful.
So I understand that C* is good only when your application does not require your data to be consistent over a period of time but reading and writing should be fast?
If my understanding is correct, please list some applications?
Cassandra does not comply with ACID like RDBMS, but CAP. Therefore, Cassandra selects AP from CAP and leaves it to the user to adjust consistency. < br>I definitely cannot use Cassandra for core banking transactions, because C* is slightly inconsistent.
But Cassandra writes very fast, which is good for OLTP.
I can use C* for OLAP because the read is very Fast, this is also good for reporting.
So I understand that C* is good only when your application does not require your data to be consistent over a period of time but reading and writing should be fast?
If my understanding is correct, please list some applications?
ACID is an attribute of relational databases, of which BASE is an attribute of most nosql databases, and Cassandra is one of them. CAP theorem just explains the consistency in distributed systems , Availability and partition fault tolerance. The good thing about Cassandra is that it has adjustable consistency, so you can be very consistent (at the cost of partition tolerance), so OLTP is feasible. As phact said, there are even some banks in Their trading software is built on top of Cassandra. OLAP is also feasible, but not only Cassandra, because its partitioned row storage limits its capabilities. You need to be able to perform complex queries like Spark.