bloglike:2021-06
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
bloglike:2021-06 [2021/06/17 04:50] – When AWS CodeBuild and CloudWatch logs integration doesn't work stybla | bloglike:2021-06 [2021/06/25 16:02] – It's a trap and its name is FIFO queue stybla | ||
---|---|---|---|
Line 39: | Line 39: | ||
--- // | --- // | ||
+ | |||
+ | |||
+ | ===== It's a trap! and its name is FIFO queue ===== | ||
+ | |||
+ | When migrating from Redis-as-a-queue to AWS SQS and making application more integrated with the cloud, we've decided to use a FIFO queue. Intentions were good - ideally keep order of messages and prevent duplicates as low as possible. We were aware of the following excerpt from FAQ: | ||
+ | |||
+ | > By design, Amazon SQS FIFO queues don't serve messages from the same message group to more than one consumer at a time. However, if your FIFO queue has multiple message groups, you can take advantage of parallel consumers | ||
+ | |||
+ | but not so much of implications, | ||
+ | |||
+ | As for the implications(which I haven' | ||
+ | |||
+ | Therefore, we've switched to the simple SQS queue with no content deduplication(which probably didn't work anyway with this setup) and no FIFO and possibility of duplicates. However, that's life and it works. | ||
+ | |||
+ | --- // |
bloglike/2021-06.txt · Last modified: 2021/06/29 03:51 by stybla