3 ms·

(Yikes) I feel compelled to remind the folks complaining about webhooks arriving out of order of the fallacies of distributed computing. https://en.wikipedia.o

(Yikes) I feel compelled to remind the folks complaining about webhooks arriving out of order of the fallacies of distributed computing. https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing https://en.wikipedia.org/wiki/Fallacies_of_distributed_compu... For goodness sakes, log webhooks to a queue and rebuild the object graph later by probing their API. I would be absolutely blown away if Stripe recommended that folks attempt to process these inline (simple tutorial-level example code notwithstanding). EDIT: And for your own sanity, assume 50% of the webhooks you expected to arrive didn't. Schedule a periodic task to scrape transactions from their API.

dbbk 8y ago
> EDIT: And for your own sanity, assume 50% of the webhooks you expected to arrive didn't. Schedule a periodic task to scrape transactions from their API. I'm pretty sure the Webhooks keep retrying until they get a success response back from your server.
- quelltext 8y ago
  They do that but not forever: https://stripe.com/docs/webhooks/best-practices#retry-logic https://stripe.com/docs/webhooks/best-practices#retry-logic
  - dbbk 8y ago
    They do it for 3 days though which seems more than enough... and you can even manually trigger them from the dashboard. So I'm not really seeing why you can't just rely on Webhooks?
    - quelltext 8y ago
      You can rely on them. I just wanted to correct what was said in that comment.
quelltext 8y ago
Yeah, this is specifically pointed out here: https://stripe.com/docs/webhooks/best-practices#acknowledge-events-immediately https://stripe.com/docs/webhooks/best-practices#acknowledge-...