Use Dead Letter Queues to save event invocation data
Serverless architectures rely heavily on asynchronous communication between functions and services.
This often creates points of failure which can leave processes in an incomplete state when messages go undelivered.
Dead Letter Queues (DLQs) can be set up to catch failed communications.
An asynchronously invoked Lambda function will be retried twice by default, but when it fails, the DLQ will catch the invocation data. We can even use SQS triggers to process these failed events.