That's a whole class of Lambda Functions. This is EXTRA nice because it allows us to specify any destination queue. Just redrive to the original queue would have been nice. Luc van Donkersgoed, lead engineer at PostNL and AWS Serverless Hero, tweets: In the configuration of a DLQ, it is possible to specify if the messages should be sent back to their source queue or another queue, using an ARN for the custom destination option.
NODE JS SEND MESSAGE TO AWS SQS QUEUE HOW TO
One of the things I never liked about using DLQs was the need to build the mechanism to re-process the items that ended up there.īenjamen Pyle, CTO at Curantis Solutions, wrote an article on how to redrive messages with Golang and Step Functions. The feature has been well received by the community with Tiago Barbosa, head of cloud and platforms at MUSIC Tribe, commenting: To reprocess DLQ messages, developers can use the following tasks: StartMessageMoveTask, to start a new message movement task from the dead-letter queue, CancelMessageMoveTask, to cancel the message movement task, and ListMessageMoveTasks, to get the most recent message movement tasks (up to 10) for a specified source queue. Do I want it? Yes! Do I want to log in to the AWS Console to use it? Absolutely not. It's not a feature, it's not an API, it's an "experience" only available in the AWS Console. In the past, it was only possible to handle messages manually in the console, with Jeremy Daly, CEO and founder of Ampt, writing at the time: Once the failed message has been debugged or the consumer application is available to consume it, the new redrive capability moves the messages back to the source queue, programmatically managing the lifecycle of the unconsumed messages at scale in distributed systems. You generally associate alarms with the DLQ to send notifications when such events happen. When ReceiveCount > maxReceiveCount, Amazon SQS moves the message to your designated DLQ for human analysis and debugging. Sébastien Stormacq, principal developer advocate at AWS, explains:Įach time a consumer application picks up a message for processing, the message receive count is incremented by 1. When errors occur, SQS moves the unconsumed message to a dead-letter queue (DLQ), allowing developers to inspect messages that are not consumed successfully and debug their application failures. The new capability allows developers to move unconsumed messages out of an existing dead-letter queue and back to their source queue. AWS recently announces support for dead-letter queue redrive in SQS using the AWS SDK or the Command Line Interface.
0 kommentar(er)
