Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and method
Start with update needs, documented capabilities and recovery of missed events. A webhook reports a change; periodic polling checks for new information. Compare acceptable delay, volume, limits and traceability. Consider combining them when a notification needs subsequent verification or reconciliation to maintain continuity across interruptions in either connected system.
Illustrative example
Illustrative example: a new order needs to reach operations promptly, while a daily report can wait. A notification triggers retrieval of the order and a periodic review detects gaps. The report uses scheduled retrieval. Both flows preserve identifiers so repeated notifications or overlapping checks do not apply the same change twice.
Acceptance check
Test missing, duplicate and delayed notifications plus interrupted polling. Measure observed delay under the intended workload without extrapolating to every possible volume. Accept when missed changes can be discovered and query demand fits known limits. Choose according to the operational requirement rather than the perceived sophistication of the technical label.
Key takeaways
- The update mechanism should include a tested way to discover missed changes.