NoSQL - How does multi table schema create data consistency issues?

Author: overexchange

Originally Sourced from:

As per this answer, it is recommended to go for single table in Cassandra.

Cassandra 3.0

We are planning for below schema:

enter image description here

Second table has composite key. PK(domain_id, item_id). So, domain_id is partition key & item_id will be clustering key.

GET request handler will access(read) two tables

POST request handler will access(write) into two tables

PUT request handler will access(write) details table(only)

As per CAP theorem,

  1. What are the consistency issues in having multi-table schema? in Cassandra...

  2. Can we avoid consistency issues in Cassandra? with these terms QUORUM, consistency level etc...