Webhooks vs Message Queues

TL;DR

Explanation

Webhook: sender makes HTTP POST to receiver's URL. Synchronous from sender's perspective. Receiver must be online and respond quickly. Retry logic: varies by provider (GitHub retries 3x, Stripe retries over 3 days). Message queue: sender publishes, broker stores, consumer reads when ready. Consumer can be offline. Decoupled. More reliable (broker persists). Choose webhook when: integrating with third-party services (Stripe, GitHub, Twilio). Choose queue when: internal service communication, high volume, consumer reliability matters. Webhook receiver should: respond 200 immediately, process async, verify signature, be idempotent.

Common Misconception

Why It Matters

Common Mistakes

• Processing webhook payload synchronously — causes timeout → provider retries → duplicates.
• Not verifying webhook signature — HMAC validation required.
• Not idempotent webhook handler — duplicate events on retry.

Code Examples

// Blocking webhook handler — times out on slow processing:
app()->post('/webhook/stripe', function($request) {
    sendConfirmationEmail($request->data); // Slow — times out, Stripe retries
    return response('OK');
});

// Return 200 immediately, process async:
app()->post('/webhook/stripe', function($request) {
    // 1. Verify signature:
    Stripe::constructEvent($request->body, $request->header('Stripe-Signature'), $secret);
    // 2. Dispatch to queue:
    Queue::dispatch(new ProcessStripeWebhook($request->data));
    return response('', 200); // Return fast
});

References

• ↗ https://stripe.com/docs/webhooks

Tags

Related Terms