How to Shrink Key Revocation Latency: Webhook Intake with a Scheduled Polling Backstop
Use the push channel for speed and a scheduled poll for proof. Registered webhooks carry a revocation from the issuer to your gateway in a couple of seconds; scheduled polling is what tells you, an hour later, whether that revocation actually landed. On a support desk product where every tenant holds its own scoped key, the axis that decides the architecture is not median latency — it's whether…
Webhooks provide fast revocation updates, while scheduled polling offers a way to verify those updates. Registered webhooks deliver low latency and natural idempotency, but they have a hard limit when retries are exhausted. Scheduled polling inverts this, offering reliability but with latency determined by the poll interval. The ideal solution combines both: the webhook provides immediate proof of revocation, while the scheduled poll acts as a backup to confirm when the revocation actually landed.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
