A practitioner argues webhooks are the wrong primitive for replication and drafts a cursor-addressed change feed instead
- Sources: primary, discussion
- Summary: The post argues that webhooks are used to replicate provider state into a local copy, a job they are not built for. It sketches a cursor-addressed change feed that a consumer reads at its own pace and resumes from a stored position.
- Why it matters: The reconciliation cron is the tell, because a nightly diff against the provider's list APIs is an admission that the local copy has no way to detect a dropped delete.