Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
10 of 486 records match.
| Kind | Record | Organisation | Year | Setup |
|---|---|---|---|---|
| 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 |
| 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 |
| Decision | Serve every Q&A site from one multi-tenant application and keep web servers overprovisioned | Stack Overflow | 2016 | Sharded |
| Decision | Use Elasticsearch for search instead of SQL Server full-text search, because SQL CPUs are expensive | Stack Overflow | 2016 | Sharded |
| Decision | Cache in two layers, a web-server HTTP cache and Redis, and clear the first layer through Redis pub/sub | Stack Overflow | 2016 | Sharded |
| Decision | Push updates to browsers over websockets, which are more efficient than polling, at the cost of load balancer port exhaustion | Stack Overflow | 2016 | Sharded |