Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
11 of 486 records match.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| Decision | Scale ZippyDB keyspaces online via logical-to-physical shard indirection and coordinator-worker resharding | Meta | 2023 | Sharded |
| Decision | Offload Instagram-to-Threads follow-graph mirroring and notifications to rate-limited Async workers | Meta | 2023 | Sharded |
| 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 |
| Failure | Database contention filled Redis memory, and a full Redis could neither accept nor release jobs | Slack | 2017 | Sharded |
| Decision | Added Kafka in front of the Redis job queue instead of replacing Redis | Slack | 2017 | Sharded |
| Decision | Enqueue path acknowledges after the Kafka leader only, trading a small risk of lost jobs for latency | Slack | 2017 | Sharded |
| Decision | Hold all state in memory behind one lock and rewrite a single JSON file on every change | Tailscale | One server | |
| Decision | Replace the rewritten JSON file with etcd as a minimal database for a single-process control plane | Tailscale | One server |