2 ms·
Clearly a lot of thought and work has been put into this and I give the authors credit for that. I appreciate any entry into the space but this is a really cro
by throwaway2016a 9y ago
Clearly a lot of thought and work has been put into this and I give the authors credit for that.
I appreciate any entry into the space but this is a really crowded space. With some very battle tested entries in the field as people have pointed out.
There are a few questions not in the readme that I think need answering for a queue system:
- Execution guarantees (at least once, at most once, exactly once?)
- Order guarantees (FIFO, approximately FIFO, nondeturministic, etc)
- Throughput compared to other systems
- Fault tolerance characteristics, how many nodes can I lose before it stops working, when it does how do I recover
As I said, I have a lot of choices in this field. I'd like to see all the data up front.
- mighty_warrior 9y agoAgreed, there are a lot of more robust products already in this space. My biggest concern is its reliance on mysql. There is no way this could be a valid option for high volume messaging when it is essentially database as a queue.