Catalogue

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

27 of 486 records match; the first 20 are shown.

KindRecordOrganisationYearSetup
Failure

Traffic peak overloaded one datacenter's load balancers while a service-mesh sidecar failed to scale, and a client retry bug amplified authentication traffic

github-2026-load-balancer-sidecar-overload#f1

GitHub2026Multi-region
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

Connection pools that recycled every 15 minutes synchronized into a thundering herd after a managed Postgres upgrade

clerk-2025-database-connection-recycling#f1

Clerk2025
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

Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them

bluesky-2025-lossy-timelines#f1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines

bluesky-2025-lossy-timelines#d1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Cache high-follow accounts in a Redis sorted set loaded into memory every 30 seconds instead of reading follow counts per write

bluesky-2025-lossy-timelines#d2peak of 100,000 requests/s or more

Bluesky2025Sharded
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

7 more records. Sign in to see all 27.