You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to enhance MongoMQ to make it more suitable as a "job queue" mechanism, for which I have often used Amazon SQS with great success.
The basic idea would be to add two features to MongoMQ which SQS has:
Support for message handled confirmation and retry semantics. SQS for instance offers a timeout after which a message is requeued for delivery some configurable number of times.
Support for "future delivery" so that message delivery can be scheduled in the future.
My belief is that both of these features can be handled with relatively minor surgery to the query MongoMQ is using to find jobs in the collection. Opening an issue before I begin adding these features to see if you have issues or suggestions on the path forward.
The text was updated successfully, but these errors were encountered:
Gladly take any enhancements on MongoMQ, I thought I was going to have time to maintain it and advance it earlier in the year, but unfortunately the project got canceled and I haven't had the time. Would even be willing to grant contributor rights on the project if your interested.
I would like to enhance MongoMQ to make it more suitable as a "job queue" mechanism, for which I have often used Amazon SQS with great success.
The basic idea would be to add two features to MongoMQ which SQS has:
Support for message handled confirmation and retry semantics. SQS for instance offers a timeout after which a message is requeued for delivery some configurable number of times.
Support for "future delivery" so that message delivery can be scheduled in the future.
My belief is that both of these features can be handled with relatively minor surgery to the query MongoMQ is using to find jobs in the collection. Opening an issue before I begin adding these features to see if you have issues or suggestions on the path forward.
The text was updated successfully, but these errors were encountered: