A declaration

Turns out I don’t really have any readers here , I guess Ill use this platform to vent my frustrations in a relatively more uncensored manner.

Been working with AWS queues all night and damn they’re weird , when you poll for only a single message , you get no messages in return even if the queue has messages in them , but if you poll for 5 messages you get every message in the queue. Ordinarily you’d expect messages to come to you irrespective of the message limit, only within it. AWS also allows you to automatically delete messages once they’re polled , but weirdly guess what : If after polling the queue for 5 messages , you poll it again , you get no message in response. But if you poll it again with a message limit of 1 message for which you get no response , but poll again for 5 messages you get the 3 messages that already were in the queue.

Besides this I had created two fifo queues with basically the same config and sent messages to both of them. For basically both queues , I had been sending messages via a Serverless function keeping the deduplication ID unique , but the message group ID common across all messages. Turns out , the first queue allows you to instantly receive all the messages at a simple poll , but the second one only allowed me to receive the first message. Well , turned out I had set the timeout for new message receive after consumption to 30 minutes for the second queue, but for the first only 30s , I have no idea how this can potentially affect other messages in the queue that are yet to be consumed. But changing it to 30s did the trick. Also making the deduplication ID and the message group ID unique across all messages kinda did the trick as well , although it is kaafi jugaadu trick.

Cloud and distributed computing can be unbearably confusing at times. This is basically not the only thing I did that kinda been messing with my head.

Interesting , I might as well use this platform to keep track of all that I learnt in tech. Feels reasonably motivating.