Digest Guarantees: How to Choose Public HTTPS Webhook Push, Subscribe, or Polling

To deliver a weekly digest for an edtech SaaS, first establish a durable ledger with unique job identities for each active customer and week. This ledger must track job states (pending, leased, delivered), attempt counts, lease expiration, and delivery timestamps. The hard boundary is the job identity, not the delivery method. Start with a polling worker, as it minimizes the number of independently failing components.

Only consider queue push or subscription delivery if measured queue delay, regional isolation, or worker operations justify these changes. Ensure the same digest_key is used for every job attempt to guarantee idempotency, even if retries occur. Define clear roles for pending, leased, delivered, and exhausted jobs to prevent duplicate records in a multi-region setup.

Finally, explicitly state acceptable delay windows and lease expiration policies to handle late arrivals or worker failures.