When NOT to use Cassandra? [closed]

Answer 1

You should ask your self the following questions:

1. (Volume, Velocity) Will you be writing and reading TONS of information , so much information that no one computer could handle the writes.
2. (Global) Will you need this writing and reading capability around the world so that the writes in one part of the world are accessible in another part of the world?
3. (Reliability) Do you need this database to be up and running all the time and never go down regardless of which Cloud, which country, whether it's VM , Container, or Bare metal?
4. (Scale-ability) Do you need this database to be able to continue to grow easily and scale linearly
5. (Consistency) Do you need TUNABLE consistency where some writes can happen asynchronously where as others need to be certified?
6. (Skill) Are you willing to do what it takes to learn this technology and the data modeling that goes with creating a globally distributed database that can be fast for everyone, everywhere?

If for any of these questions you thought "maybe" or "no," you should use something else. If you had "hell yes" as an answer to all of them, then you should use Cassandra.

Use RDBMS when you can do everything on one box. It's probably easier than most and anyone can work with it.