This project is no longer actively supported. It is made available as read-only. A highly available, horizontally scalable queuing and notification service compatible with AWS SQS and SNS
When using lists we need to maintain two extra objects to deal with delayed and invisible messages (this could likely be consolidated to one extra object). We also need to have regular maintenance tasks that search for invisible messages and make them visible again.
I propose that we should evaluate using a sorted set data structure with visibility time as the score and the message id as the member value. This will allow us to do away with the other data structures and housekeeping tasks.
When using lists we need to maintain two extra objects to deal with delayed and invisible messages (this could likely be consolidated to one extra object). We also need to have regular maintenance tasks that search for invisible messages and make them visible again.
I propose that we should evaluate using a sorted set data structure with visibility time as the score and the message id as the member value. This will allow us to do away with the other data structures and housekeeping tasks.