Cassandra Internals

Consistency level:

Tuneable with trade off from availability in the CAP theorem. Provides Eventual Consistency.
The highest consistency level does not guarantee perfect consistency due the lack of rolling back or WAL (write ahead logs) mechanism found in tradition RDBMS.

For more, read here.

Partition/Hashing mechanism:

Similar to the Chord protocol.

For more, read here

Membership Protocol (Failure detection):

Similar to the Gossip membership protocol.

For more, read here.

Request ordering:

Does not use Causality-based method such as Lamport/Vector timestamps.
Instead uses a “Last one wins” competition strategy and use clock synchronisation.

Fore more, read here.

More concepts to be added….

Leave a comment

Your email address will not be published. Required fields are marked *