3 ms·
> At that time, we began processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS servi
by nfRfqX5n 3y ago
> At that time, we began processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services. As of 3:37 PM, the backlog was fully processed
pretty cool that stuff was stored in a backlog and eventually processed!
- capableweb 3y agoI don't want to diminish anything, but in terms of dealing with queues, backlogs are pretty much a basic requirement from the beginning.
- great_psy 3y agoI am guessing they mean SQS queue … so basically the SQS aid doing what is supposed to: - try to process event - send to DLQ if it fails - there’s a redrive button in the DLQ to … well restive the events after the lambda is fixed