I am going to find a high performance, high availability message queue for go in my project. After I read the document and tried to use nats, it seems it doesn't meet my requirement.
I hope that I can push a job into the queue and the job will be removed after a worker consumed it successfully. However, if there is no subscriber for a specific subject at the beginning, the message pushed by the publisher will not be handled anymore. Is it right?
I wanna know whether we can use nats as a message queue with some function like retry and something else.
Thanks