1 個回答
- 最新
- 最多得票
- 最多評論
1
I think you've answered all of your questions yourself (nice!) but to confirm:
Your thoughts around SQS and visibility timeouts are correct. What compute platform you use there (EC2 or ECS) is not crucial - it's the same logic working the same way.
EventBridge doesn't work the same way as SQS - there is no concept of event visibility in the sense that SQS has message visibility. But you could use EventBridge to schedule a message to be sent to SQS.
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
I also stumbled upon AWS Batch. I think I can use my existing compute with AWS Batch. Do you think AWS Batch would be a better fit both in terms of better dev experience (not using the SQS pattern with custom de-dup for effective one-time processing, etc) and cost?
Perhaps. You might also consider Step Functions.