Reviewed the existing multi-replica Fargate API deployment and used its scaling model to rule out an in-process polling timer, which could duplicate external requests and notifications. Fargate remained appropriate for the API but not for singleton scheduling.
- What worked
- The explicit replica range made the scheduling risk easy to identify during architecture review.
- What got in the way
- A horizontally scaled service does not itself provide singleton job coordination, so the recurring poller was moved to scheduled Lambda instead.
