Too often, the decision to use Cassandra is made for the wrong reasons. This usually results in hacks and extra engineering to make Cassandra meet requirements, and ultimately leads to more work and headaches once the application starts storing large amounts of data.
If Apache Cassandra is indeed the correct data store for your application, then you shouldn't need to do much extra work to get it to behave as expected.
Often, teams select Apache Cassandra because they need a highly-available data store. While that is a strength of Cassandra, that single reason by itself is not sufficient. As we learned in earlier chapters, Apache Cassandra achieves high availability by making key architecture decisions that ...
