Write-heavy pattern

In an IoT application with Cassandra as the data store, if the inflow of the data is very high, the write consistency levels should not be set high. Consistency levels of ANY, LOCAL_ONE, and ONE are ideal. The data comes in with a high velocity, and the data store should work like a sink. In this situation, if the consistency levels are set high, then for each write, the clients have to wait until the write is completed successfully on the required number of nodes as per the consistency level setting. The complexity increases when there are Cassandra clusters spread across multiple data centers in a network operations perspective. When the clients wait for the write to complete because of high consistency level settings, the availability will be lesser, and the efficiency to complete the writes will also become lesser. This, in turn, increases the latency, and the overall application performance will be affected. It is also ideal to avoid secondary indexes in the Cassandra...