Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
30 of 486 records match; the first 20 are shown.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| 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 | Tarpit rate limiting held sockets open until the load balancers ran out of connection slots and rejected real traffic | Healthchecks.io | 2025 | |
| Decision | Answer rate-limited requests with an immediate HTTP 429 instead of tarpitting them | Healthchecks.io | 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 | |
| Decision | Move rate-limit state from MariaDB tables to Redis with per-key TTLs | Let's Encrypt | 2025 | |
| Decision | Replace week-long sliding-window counters with GCRA virtual scheduling | Let's Encrypt | 2025 | |
| Decision | Pause failing zombie clients by tracking consecutive ACME challenge failures per account and domain | Let's Encrypt | 2025 | |
| 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 | Store user segment membership for 270M+ users in roaring bitmaps downloaded from S3 at startup instead of Bloom filters | Grab | 2023 | Sharded |
| Decision | Enforce per-user frequency caps with a Redis sorted-set sliding log instead of DynamoDB or a sliding window limiter | Grab | 2023 | Sharded |
| Decision | Preload the Lua script via SCRIPT LOAD and pipeline per-user EVALSHA calls to avoid Redis Cluster CROSSSLOT errors | Grab | 2023 | Sharded |
| Failure | A bug in per-tenant limit enforcement let one tenant overload a shared cluster, and error handling made the overload spread | Grafana Labs | 2021 | Multi-region |
| Decision | Share metrics clusters between tenants under per-tenant data and rate limits, and size clusters partly from those limits | Grafana Labs | 2021 | Multi-region |
| 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 |
10 more records. Sign in to see all 30.