Do you also store events in Cassandra? If yes, why not to add "processed" flag to existing table(s), and fetch non-processed events with single SELECT?
Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting ---- On Fri, 24 Feb 2017 06:24:09 -0500 Vincent Rischmann <m...@vrischmann.me> wrote ---- Hello, I'm using a table like this: CREATE TABLE myset (id uuid PRIMARY KEY) which is basically a set I use for deduplication, id is a unique id for an event, when I process the event I insert the id, and before processing I check if it has already been processed for deduplication. It works well enough, but I'm wondering which compaction strategy I should use. I expect maybe 1% or less of events will end up duplicated (thus not generating an insert), so the workload will probably be 50% writes 50% read. Is LCS a good strategy here or should I stick with STCS ?
