Catalogue
- Cards
- 165
- Records
- 486
- Workloads
- 19
- Corpus version
- 74847648e25a
18 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 | Move the public sites from bare-metal data centers to Kubernetes in one GCP region, using Windows Kubernetes for legacy .NET apps | Stack Overflow | 2025 | One site |
| Decision | Run SQL Server on dedicated high-memory GCP VMs with half the CPU cores disabled instead of managed cloud SQL | Stack Overflow | 2025 | One site |
| Decision | Use GCP MemoryStore for Redis with key prefixes instead of self-hosting Redis on Kubernetes | Stack Overflow | 2025 | One site |
| Decision | Self-host Elasticsearch on Kubernetes with the ECK operator instead of using Elastic Cloud | Stack Overflow | 2025 | One site |
| Decision | Load-test the cloud stack in isolated Terraform-built environments matching production before migrating | Stack Overflow | 2025 | One site |
| Decision | Plan to put public assets behind Cloudflare CDN and process its logs in Snowflake, retiring HAProxy logs and TPS | Stack Overflow | 2025 | One site |
| Decision | Package cross-cloud deployments in CNAB containers deployed via Octopus Deploy and GitHub Actions | Stack Overflow | 2025 | One site |
| 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 |
| 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 |