medium10 pts · first answer countsmessagingserverless
SQS messages processed twice
Workers take up to 90 seconds per job, and the SQS queue visibility timeout is 30 seconds. Jobs are often run twice. What should you do?
Discussion 0
Join free to post in the discussion.
Related questions
- How serverless functions are billedCloud Engineer
- Reducing serverless cold startsCloud Engineer
- Lambda in a VPC cannot reach an APICloud Engineer
- Lambda spike breaks the databaseCloud Engineer
- FIFO queue backlog with idle workersCloud Engineer
- Too many database connectionsFull Stack Developer
- Alerting on queue lagSite Reliability Engineer
- Pick the strongest value propositionBusiness Development Manager