News for hackers. Stuff that matters.
Re:Webhooks do’s and dont’s: what we learned after integrati... by jon-wood on Tuesday November 22, 2016 @01:43PM (#13016372)
It's not AMQP (sadly) but something I've done previously is to have the actual webhook endpoint be as dumb as possible, doing nothing but accepting the payload (maybe with some very high level validation that the request was expected) and pushing it into a real queueing system.

This means you can handle all sorts of failure modes, not just the backend going down, but also bugs in the consumer that would otherwise result in losing the request. I've not tried it, but I imagine this is a pretty good usecase for AWS Lambda as it's a small bit of glue code.

Re:Webhooks do’s and dont’s: what we learned after integrati... by stephenr on Wednesday November 23, 2016 @01:23AM (#13020528)
I've used the same basic concept for accepting payment-received notifications (from a http redirect based payment gateway):

Read the transaction ID from the request body, and store it (with a date/time) in a table. A periodic process later checks them, and uses the payment service's API to validate the payment is valid and take appropriate action.

Re:Webhooks do’s and dont’s: what we learned after integrati... by fiatjaf on Tuesday November 22, 2016 @06:38PM (#13018646)
Shameless plug: https://requesthub.xyz is ideal for these cases.
Re:Webhooks do’s and dont’s: what we learned after integrati... by jon-wood on Wednesday November 23, 2016 @09:22AM (#13022793)
That's pretty awesome, thanks for the tip.