FIFO & Exactly Once Processing

[CGDS]

In the best practices section of the wiki and in #257, it talks about the importance of writing idempotent jobs as a consequence of SQS queues only guaranteeing at least once delivery. Since shoryuken also supports the newer FIFO queues now though, which do support exactly once processing, it seems like the documentation could use a little brushing up to mention the other option. If I got that right, that is. Mind if I open a PR?

[phstc]

Mind if I open a PR?

@CGDS please 🙏 Actually for wiki pages, you don't need to PR, you can just update them!

Even with FIFO queues, it is still important to write idempotent workers, for example: in case a worker fails and you need to retry a partially executed message, if the visibility timeout expires etc. Besides that, FIFO only prevents dups sent within a 5 minutes interval as long as you use a valid "Message Deduplication ID".

[CGDS]

Good point(s)
Made an edit, please feel free to revert or modify as you please

[phstc]

Hi @CGDS

Which wiki did you change? I would love to have a 👀

I couldn't find updates here.

[phstc]

NVM just found it https://github.com/phstc/shoryuken/wiki/Best-Practices

Thanks ❤️

In the best practices section of the wiki

I missed that part.