Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
27 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| 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 | Multi-region |
| Decision | Own the webhook pipeline after customers could not see what happened to a webhook, leaving a hosted queue | Marble | 2026 | |
| Decision | Workers atomically claim a delivery before sending so overlapping workers or retried queue messages do not send duplicates | Marble | 2026 | |
| Failure | Connection pools that recycled every 15 minutes synchronized into a thundering herd after a managed Postgres upgrade | Clerk | 2025 | |
| Failure | One customer's endpoint outage made deliveries time out, filled the shared worker pool and delayed Directory Sync webhooks for everyone | WorkOS | 2025 | |
| Failure | Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them | Bluesky | 2025 | Sharded |
| Decision | Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines | Bluesky | 2025 | Sharded |
| 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 | Sharded |
| 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 | |
| Decision | Per-customer SQS queue and Lambda handler replace one shared RabbitMQ queue so slow or heavy customers stop delaying others | Dwolla | 2019 | |
| Decision | Pre-create disabled per-customer resources and toggle the event source mapping instead of creating and deleting them on subscribe | Dwolla | 2019 | |
| Decision | Give every destination its own queue and service so one slow destination cannot delay the rest | Twilio Segment | 2018 | |
| Decision | Split each destination's code into its own repo to isolate test failures | Twilio Segment | 2018 | |
| Decision | Consolidate the over 140 destination services into one service, with Centrifuge planned to replace the queues | Twilio Segment | 2018 | |
| Decision | Merge all destination code into one repo with a single version of every dependency | Twilio Segment | 2018 | |
| Decision | Record and replay destination HTTP traffic in tests so the merged repo's suite is fast and reliable | Twilio Segment | 2018 | |
| Decision | One reader per shard replaces one reader thread per customer webhook after delays reached 10 minutes | Nylas | 2018 | Sharded |
| Decision | Kinesis chosen over the MySQL binlog and Kafka as the ordered source of changes, mainly for operational simplicity | Nylas | 2018 | Sharded |
| Decision | New sender ran two months in a simulated mode that sent nothing, compared against the legacy sender, before cutover | Nylas | 2018 | Sharded |
| Failure | Resuming from the last sent MySQL auto-increment id made the new webhook sender skip transactions in testing | Nylas | 2018 | Sharded |
7 more records. Sign in to see all 27.