On Tue, Mar 24, 2015 at 5:05 AM, Robin Verlangen <ro...@us2.nl> wrote:
> - for every point in the future there are probably hundreds of actions > which have to be processed > - all actions for a point in time will be processed at once (thus not > removing action by action as a typical queue would do) > - once all actions have been processed we remove the entire row (by key, > not the individual columns) > I've used Cassandra for similar queue-like things, and it's "fine." Not ideal, but number of objects and access patterns are "fine." https://engineering.eventbrite.com/replayable-pubsub-queues-with-cassandra-and-zookeeper/ This design never truncates history, but if you can tolerate throwing away history, that problem goes away.. =Rob
