shineDaPoker

3 ms·

1. 1.▲
   by shineDaPoker 8mo ago

   This matches my thinking. The retrieval/lookup approach is exactly what I built - basically Option C with an observe-before-act pattern. For APIs that support idempotency keys (Stripe, etc.), I use those. For ones that don't but h
2. 2.▲
   by shineDaPoker 8mo ago

   I actually talked to someone in temporal about this recently. Temporal gives you the primitives to handle it (activities, configure retries, interceptors), but you still have to implement the deduplication logic yourself for each external i
3. 3.▲
   by shineDaPoker 8mo ago

   This is exactly the approach I took. Proxy layer that: - Uses atomic records (fence tokens) to prevent concurrent execution - Checks external system first before retrying (the retrieval step) - Records result for future lookups The atomic r
4. 4.▲
   Ask HN: How do you handle duplicate side effects when jobs, workflows retry?

   11 points by shineDaPoker 8mo ago|11 comments
5. 5.▲
   Show HN: Verity – I got tired of debugging duplicate emails after job restarts(useverity.io)

   1 points by shineDaPoker 8mo ago|0 comments