A recurring cleanup trigger is easiest to reason about when the scheduler owns time and your public HTTP endpoint owns one bounded operation. For a healthtech shipment service, that means a cron request can remove expired delivery records, record an idempotency key, and return quickly; it should not become a disguised task executor.
The practical choice is an HTTP cron schedule for periodic cleanup, with a queue and worker only when the cleanup can exceed the scheduler's 900-second execution limit. Keep the shipment notification fan-out separate from deletion: publish one durable message per subscriber, let the delivery path use a realtime channel when the recipient is connected, and make every consumer safe to run twice.
The trigger should stay small.
Infrai fits this narrow handoff when a team wants the cron, queue, and realtime surfaces behind one REST API and one key.…