Show HN: Sandglass – Distributed, scalable, persistent time-sorted message queue
This looks promising.I'm currently dealing with a queuing-related issue.I have a series of tasks running across servers that consume from a queue and run a task.Often, these tasks die mid-execution (but can be resumed by any other server). So, the queue is a database, and the running tasks "touch" a timestamp in the database if they are still executing. When a database document hasn't been updated for a while, the "consumption query" makes it so that it is 'redelivered' to an available server listening to the "queue".Of course, this is subpar, but we haven't yet come across an elegant (and not too over-engineered) way to replace this.