We are considering using Cassandra and I want to make sure our use case fits Cassandra's strengths. We have the table like:
user_id | question_id | result | created_at
Where our most common query will be something like:
SELECT * FROM answers WHERE user_id = 123 AND created_at > '01/01/2012' AND created_at < '01/01/2013'
Sometimes we will also limit by a question_id or a list of question_ids.
Secondary indexes will be created on user_id and question_id. We expect the upper bound of number of answers for a given user to be around 10,000.
Now my understanding of how Cassandra will run the aforementioned query is that it will load all the answers for a given user into memory using the secondary index, then scan over that set filtering based on the dates.
Considering that that will be our most used query and it will happen very often, is this a bad use case for Cassandra?
Thanks for the help.