sandglass

Would like to know this as well. I have been on the lookout for a similar system to SideKiq. Unfortunately for Go, there isn't anything that matches it 100%. I have looked into: https://github.com/celrenheit/sandglass https://github.com/RichardKnop/machinery https://github.com/contribsys/faktory In the end I went with machinery due to supporting: - Batches (or Groups, tasks executed at the same time) - Chains (tasks executed one by one) - Callbacks (a task executed, on completion of a Batch) - Cron Jobs - Rescheduling failed jobs - Long-runnng Jobs - Distributed/Fault Tolerant DB (for Jobs) - Distributed/Fault Tolerant Workers + other things I cant remember now. It would be very interesting to know if this is going to be opened sourced and whether it supports the list above.

By setting aside the availability, it should be rememberable (for me it is either an animal or an object/person that represents the product/project). Lately, I chose the name Sandglass for a message queue (https://github.com/celrenheit/sandglass). The reason is that this project depends on an ID generator that I named sandflake (in reference to twitter's snowflake). So I chose the name sandglass because it is kind of like a glass with a lot of sandflakes flowing through it (like a message queue). Another name I used was Lion for an http router but for no particular reasons :)

I worked mainly on open source side projects such as: Sandglass https://github.com/celrenheit/sandglass a distributed, horizontally scalable, persistent, time ordered message queue. It was developed to support asynchronous tasks and message scheduling which makes it suitable for usage as a task queue. Sandflake https://github.com/celrenheit/sandflake decentralized, sequential, lexicographically sortable unique id.

It seems like it uses rocksdb for persistance. https://github.com/celrenheit/sandglass/blob/dev/storage/roc...