Catalogue

Cards
165
Records
486
Workloads
19
Corpus version
74847648e25a
Workload
Kind
Setup

11 of 486 records match.

KindRecordOrganisationYearSetup
Failure

Users who follow hundreds of thousands of accounts made hot shards that slowed the timelines sharing them

bluesky-2025-lossy-timelines#f1peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

Drop timeline writes with a probability set by how many accounts a user follows, accepting imperfect timelines

bluesky-2025-lossy-timelines#d1peak of 100,000 requests/s or more

Bluesky2025Sharded
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-lossy-timelines#d2peak of 100,000 requests/s or more

Bluesky2025Sharded
Decision

One reader per shard replaces one reader thread per customer webhook after delays reached 10 minutes

nylas-2018-webhooks#d1

Nylas2018Sharded
Decision

Kinesis chosen over the MySQL binlog and Kafka as the ordered source of changes, mainly for operational simplicity

nylas-2018-webhooks#d2

Nylas2018Sharded
Decision

New sender ran two months in a simulated mode that sent nothing, compared against the legacy sender, before cutover

nylas-2018-webhooks#d3

Nylas2018Sharded
Failure

Resuming from the last sent MySQL auto-increment id made the new webhook sender skip transactions in testing

nylas-2018-webhooks#f1

Nylas2018Sharded
Decision

Serve every Q&A site from one multi-tenant application and keep web servers overprovisioned

stackoverflow-2016-architecture#d1peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Use Elasticsearch for search instead of SQL Server full-text search, because SQL CPUs are expensive

stackoverflow-2016-architecture#d2peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Cache in two layers, a web-server HTTP cache and Redis, and clear the first layer through Redis pub/sub

stackoverflow-2016-architecture#d3peak under 10,000 requests/s

Stack Overflow2016Sharded
Decision

Push updates to browsers over websockets, which are more efficient than polling, at the cost of load balancer port exhaustion

stackoverflow-2016-architecture#d4peak under 10,000 requests/s

Stack Overflow2016Sharded