Catalogue

Cards
165
Records
486
Workloads
19
Corpus version
74847648e25a
Workload
Kind
Setup

18 of 486 records match.

KindRecordOrganisationYearSetup
Decision

Own the webhook pipeline after customers could not see what happened to a webhook, leaving a hosted queue

marble-2026-webhooks#d1

Marble2026
Decision

Workers atomically claim a delivery before sending so overlapping workers or retried queue messages do not send duplicates

marble-2026-webhooks#d2

Marble2026
Failure

One customer's endpoint outage made deliveries time out, filled the shared worker pool and delayed Directory Sync webhooks for everyone

workos-2025-directory-sync-webhooks#f1

WorkOS2025
Failure

A surge of duplicate webhooks and the retry setup filled one queue's provider quota, so new events were not delivered for hours

onfido-2024-webhooks#f1

Onfido2024
Decision

Per-customer SQS queue and Lambda handler replace one shared RabbitMQ queue so slow or heavy customers stop delaying others

dwolla-2019-webhooks#d1

Dwolla2019
Decision

Pre-create disabled per-customer resources and toggle the event source mapping instead of creating and deleting them on subscribe

dwolla-2019-webhooks#d2

Dwolla2019
Decision

Give every destination its own queue and service so one slow destination cannot delay the rest

segment-2018-goodbye-microservices#d1peak of 100,000 requests/s or more

Twilio Segment2018
Decision

Split each destination's code into its own repo to isolate test failures

segment-2018-goodbye-microservices#d2peak of 100,000 requests/s or more

Twilio Segment2018
Decision

Consolidate the over 140 destination services into one service, with Centrifuge planned to replace the queues

segment-2018-goodbye-microservices#d3peak of 100,000 requests/s or more

Twilio Segment2018
Decision

Merge all destination code into one repo with a single version of every dependency

segment-2018-goodbye-microservices#d4peak of 100,000 requests/s or more

Twilio Segment2018
Decision

Record and replay destination HTTP traffic in tests so the merged repo's suite is fast and reliable

segment-2018-goodbye-microservices#d5peak of 100,000 requests/s or more

Twilio Segment2018
Decision

One reader per shard replaces one reader thread per customer webhook after delays reached 10 minutes

nylas-2018-webhooks#d1

Nylas2018Sharded
Decision

Kinesis chosen over the MySQL binlog and Kafka as the ordered source of changes, mainly for operational simplicity

nylas-2018-webhooks#d2

Nylas2018Sharded
Decision

New sender ran two months in a simulated mode that sent nothing, compared against the legacy sender, before cutover

nylas-2018-webhooks#d3

Nylas2018Sharded
Failure

Resuming from the last sent MySQL auto-increment id made the new webhook sender skip transactions in testing

nylas-2018-webhooks#f1

Nylas2018Sharded
Decision

Replace self-hosted beanstalkd and a Ruby packager with Kinesis, SQS and a Go consumer before the system gave severe problems

pusher-2020-webhooks-kinesis#d1peak under 100,000 requests/s

Pusher
Decision

Run the new pipeline alongside the old in production without sending webhooks, then cut over in one configuration change

pusher-2020-webhooks-kinesis#d2peak under 100,000 requests/s

Pusher
Decision

Divide the event stream into locked logical shards so that one packager sees all of a channel's events and can debounce them

pusher-2020-webhooks-kinesis#d3peak under 100,000 requests/s

Pusher