IntegrationAdvanceddeduplicationwebhookcache
Implement request deduplication cache for REST webhook storm protection
Real World Scenario
Partner retries same Order webhook 50 times in 2 minutes; duplicate Order records created despite idempotency intent.
Expected Answer
• Redis or Platform Cache key webhook-id TTL 24 hours
• Return 200 OK same body for duplicate within TTL
• Idempotency-Key header standard partner contract
• Unique external ID upsert second line defense
• Rate limit partner IP 100 requests minute
• Alert duplicate rate spike indicating partner bug
• Load test retry storm 10x duplicate delivery
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Redis or Platform Cache key webhook-id TTL 24 hours. Return 200 OK same body for duplicate within TTL. Pick based on your integration pattern and team capability. Webhook dedup cache is first line; upsert external ID is second—both required. Optimize for scale and operational observability.
Architect Perspective
Webhook dedup cache is first line; upsert external ID is second—both required.